Home
Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL DevOps Test Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
Testing with DevOps Test Embedded for Eclipse IDE
Read these topics to learn how to use the product.
Application monitoring
With HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE) you can monitor the global variables of cyclic executive applications and apply user actions.
Test automation commands for running monitoring scripts and creating reports
You can run automatic monitoring scripts with commands by using a .jar file that contains libraries. You must set several parameters to run a monitoring script and generate a report.

Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL DevOps Test Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
- Testing with DevOps Test Embedded for Eclipse IDE
  Read these topics to learn how to use the product.
  - Getting started with DevOps Test Embedded for Eclipse IDE
    HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE) is designed to integrate into your existing Eclipse-based tool chain. Use this section as a guide to a typical workflow for testing and evaluating your C source code in the Eclipse CDT environment.
  - Importing C projects
    You can either create a new C project with the Eclipse CDT tools or you can import your existing C source files or Eclipse projects into your HCL DevOps Test Embedded (Test Embedded) workspace.
  - Importing DevOps Test Embedded examples
    Test Embedded is provided with several sample projects to help you get started.
  - Analyzing source code
  - Coupling Analysis overview
    Coupling Analysis consists of Control Coupling and Data Coupling.
  - Application Profiling
    Application Profiling is gathering the main features that provide profiling information at the application level: the Worst Stack Size feature and the Worst performance (coming soon) feature.
  - Testing software components
    Component testing provides a unique, fully automated, and proven solution for applications written in C/C ++, dramatically increasing test productivity.
  - Application monitoring
    With HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE) you can monitor the global variables of cyclic executive applications and apply user actions.
    - Prerequisites to monitoring applications
      Before you can monitor a cyclic executive application, you must import your project to HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE), configure Test Embedded for Eclipse IDE and your application, and build your project.
    - Recording a monitoring script
      With HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE), you can monitor a cyclic executive application that is running on a target computer and connected to Test Embedded for Eclipse IDE. You can apply user actions while you monitor the application and see the results in a dynamic graph.
    - Modifying the recorded data in a monitoring script
      You can modify the user actions and the input values that are recorded in a monitoring script and that persist as the default values in the script. When you run the updated monitoring script, the new input values and user actions are used as reference data to monitor the application.
    - Monitoring script files: Edits and updates
      When you monitor an application in HCL DevOps Test Embedded (Test Embedded), multiple files are created. You can find important information about each file, its use, its format and the parameters that you can use to update the editable files.
    - Test automation commands for running monitoring scripts and creating reports
      You can run automatic monitoring scripts with commands by using a .jar file that contains libraries. You must set several parameters to run a monitoring script and generate a report.
    - HTML monitoring reports
      When you run a monitoring script while running your application, all events are recorded in an HTML report, which automatically opens when the script is complete. The .HTML report file is saved in the Project Explorer view.
- DevOps Test Embedded Studio Overview
  HCL DevOps Test Embedded Studio (Test Embedded Studio) is the classic user interface that supports C, C++, Ada test and analysis tools.

Test automation commands for running monitoring scripts and creating reports

You can run automatic monitoring scripts with commands by using a .jar file that contains libraries. You must set several parameters to run a monitoring script and generate a report.

To run test scripts and generate result reports from commands, you must use the MonitoringPlayer.jar file that is saved with the installation files in one the following folders:

Windows: <Test Embedded installation directory>/bin/intel/win32/MonitoringPlayer.jar.
Linux: <Test Embedded installation directory>/bin/intel/linux_64/MonitoringPlayer.jar

In the Windows command line or Linux shell, enter a command to run a script or generate a report.

Enter the following command to see all the available parameters and options:
```
java -jar MonitoringPlayer.jar
```
The command generates a list of files that are used to monitor an application:
- mntfile
- inputfile
- output file
- template file
See Monitoring script files: Edits and updates to read the details about each file.
Enter the following command to run the mnt script. No report is generated. Log traces are displayed when the connection to the application finishes and when the script run is complete.
```
java -jar MonitoringPlayer.jar <mnt file> <inputfile>
```
Enter the following command to run the mnt script and generate a JSON report. Log traces are displayed to show when connection to application finishes, and when the test run is complete.
```
java -jar MonitoringPlayer.jar <mnt file> <inputfile> <outputfile>
```
See an example of JSON report that can be generated:
Enter the following command to run the mnt script and generate an HTML report:
```
java -jar MonitoringPlayer.jar <mnt file> <inputfile> <outputfile> <template file>
```

Important: Add quotation marks to the parameter values if they contain spaces.

The default report is saved to <Test Embedded installation directory>/bin/intel/win32/reports/monitoring.template or <Test Embedded installation directory>/bin/intel/linux_64/reports/monitoring.template.

See an example of an HTML report: