Home
Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL OneTest™ Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
Testing with Studio
Analyzing static source code
Code review
Code review overview

Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL OneTest™ Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
- Testing with HCL OneTest™ Embedded for Eclipse IDE
  Read these topics to learn how to use the product.
- Testing with Studio
  - HCL OneTest™ Embedded Studio overview
    HCL OneTest™ Embedded Studio is the classic user interface that supports C, C++, Ada test and analysis tools.
  - Analyzing static source code
    - Checking with static analysis
    - Static metrics
    - Code review
      - 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, HCL OneTest™ 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, HCL OneTest™ Embedded provides some additional coding guidelines, which are referenced with an E prefix.
      - Configuring code review 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.
      - Running a code review
      - Executing the code review from a script
        You can execute the build from HCL OneTest™ 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
  - Test script languages

Code review overview

Code Review for C

Automated source code review is a method of analyzing code against a set of predefined rules to ensure that the source adheres to guidelines and standards that are part of any efficient quality control strategy. HCL OneTest™ Embedded provides an automated code review tool, which reports on adherence to guidelines for your C source code.

Among other guidelines, the code review tool implements rules from the MISRA-C:2004 standard, Guidelines for the use of the C language in critical systems.

Code Review supports C89 and C99.

How the code review tool works

When an application or test node is built, the source code is analyzed by the code review tool. The tool checks the source file against the predefined rules and produces a .crc report file that can be viewed and controlled from the HCL OneTest™ Embedded graphical user interface (GUI).

Code review can be performed each time a node is built, but can also be calculated without executing the application.


To learn about	See
Setting up the rules to used for reviewing code	Configuring code review rules
Performing a code review	Running a code review
Viewing and understanding the results of a code review	Viewing code review results
Interpreting code review reports	Understanding code review reports
Locally disabling a rule	Ignoring rules in a portion of code
The list of rules used by HCL OneTest™ Embedded code review	Code review rules