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
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.

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
      - Using a customized naming script file
        In HCL OneTest™ 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.
      - 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

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.

Note: The following procedure is for advanced-users.

When crccc has been used, use crcld as follows:

crcld -xref="<model_file>.pl" "<crccc_result_file>.xob" -RULE="<confrule file>.xml" -TEST

<model_file>.pl file will be generated, it contains data needed to perform custom namecheck rule.
A file named <model_file>.R99.1.xob will be generated, it will be used on a final step when executing crcld.

Use this xob file for the next call of crcld:

crcld -crc="<crc_file_name>.crc" "<all other xob file name>.xob" "<model_file>.R99.1.xob" -RULE="<confrule_file>.xml" -TEST