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.
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.
Analyzing static source code
Code review overview
Code review settings
You can configure the code review settings before running your application in HCL DevOps Test Embedded (Test Embedded).

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.
- 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.
  - 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.
  - Analyzing static source code
    - Checking with static analysis
    - About Static Metrics
    - Code review overview
      - Code review MISRA 2004 rules
        The code review tool covers rules from the lists the rules that produced and error or a warning. Each rule can be individually disabled or assigned a Warning or Error severity by using the Rule configuration window. Some rules also have parameters that can be changed. Among other guidelines, the code review tool implements most rules from the MISRA-C:2004 standard, "Guidelines for the use of the C language in critical systems". These rules are referenced with an M prefix. In addition to the industry standard rules, Test Embedded provides some additional coding guidelines, which are referenced with an E prefix.
      - Code review MISRA 2012 rules
        The code review tool covers rules from the lists the rules that produced and error or a warning. Each rule can be individually disabled or assigned a Warning or Error severity by using the Rule configuration window. Some rules also have parameters that can be changed. Among other guidelines, the code review tool implements most rules from the MISRA-C:2012 standard, "Guidelines for the use of the C language in critical systems". These rules are referenced with an M prefix. In addition to the industry standard rules, Test Embedded provides some additional coding guidelines, which are referenced with an E prefix.
      - Annex to MISRA 2012 Rule 1.3
        This annex gives details about MISRA 2012 Rule 1.3.
      - Configuring code review rules
      - Using a customized naming script file
        In HCL DevOps Test Embedded Studio (Test Embedded Studio), you can edit and customize a Perl Naming script file to check your own naming rules (code custom naming rules U99.1). You must set the path to this customized naming script file in the code review settings to check your naming rules.
      - Code review deviations
        In some cases, it can be useful to temporarily ignore a rule non-compliance on a short portion of source code, while documenting the reason why you are allowing this deviation.
      - Code review settings
        You can configure the code review settings before running your application in HCL DevOps Test Embedded (Test Embedded).
      - Running a code review
      - Executing the code review from a script
        You can execute the build from HCL DevOps Test Embedded Studio (Test Embedded Studio) graphical interface or for advanced users, from the command line interface.
      - Running complete verification of MISRA rules from an application node
        To get a complete verification of MISRA rules, you must run the code review from an application node.
      - Viewing code review results
      - Understanding code review reports
      - Customizing the code review report
        The default code review report is generated in an HTML format from a template named misrareport.template as that you can modify to customize the code review reports.
  - Analyzing running applications
  - Testing software components
  - Using the graphical user interface
  - Tests linked to requirements
    With HCL DevOps Test Embedded (Test Embedded), you can link a test case or a service to one or several requirements that come from another tool to create a traceability matrix between requirements and test results.
  - Test script languages

Code review settings

You can configure the code review settings before running your application in HCL DevOps Test Embedded (Test Embedded).

The following options must be set from the Build settings tab in the Properties window. To open Build settings tab:

In the project explorer, right-click the project on which you want to change the settings and click Properties. Alternatively, you can select the project, and then click the settings icon on the toolbar.
Expand C/C++ Build in the left panel, select Settings.
In the right panel, in the Build tab, expand Settings and select Code Review.
Expand Code review to access the code review settings.

Additional included system directories: This option provides additional directories where system include files that is, include files between ‘<’ and ‘>' found.; For example Additional included system directories is required if your TDP is not complete .

Review included system files: Select ‘Yes’ if you want that the system include files that is include files between ‘<’ and ‘>’ must be analyzed. The default value is ‘No’.

Pre-include files: This option allows to select one or several file that are analysed before starting the code review. This is useful to define some pragmas used by the analyser.

Display errors/warnings

This option allows to control the number of error and warning messages the tool can display for each analyzed file as following:

‘All’ display all error and warning message.
‘No’ hide the error and warning message.
‘Max n' display only the n first error and warning message.

Naming script file: This option provide a perl script file for your naming rules.

Report Template: An HTML code review report is automatically generated after each execution. This report is based on a template as default <installation folder>/lib/reports/misrareport.template. You can make a copy of this template and modify it. This option is used to point to the new template file.