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 running applications
Code coverage
Coverage types
C++ coverage
Template instrumentation

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
  - Analyzing running applications
    - Runtime analysis overview
    - Profiling shared libraries
    - Code coverage
      - Code coverage overview
        Source code coverage consists of identifying which portions of a program are executed or not during a given test case. Source code coverage is recognized as one of the most effective ways of assessing the efficiency of the test cases applied to a software application.
      - Information Modes
      - Coverage types
        Ada coverage
        C coverage
        C++ coverage
        Block coverage
        Method coverage
        Condition coverage
        Template instrumentation
        Additional Statements
      - Using the Code Coverage Viewer to view reports
      - Coverage source report
      - Coverage rates report
      - Bitwise MC/DC coverage
        Put your short description here; used for first paragraph and abstract.
      - On-the-fly code coverage
      - Code Coverage Dump Driver
      - Cleaning code coverage report files
      - Justification of non-covered lines of code
      - Code coverage for assembler source files
        From HCL OneTest™ Embedded V8.3.0, you can collect coverage metrics for assembler source files. Coverage information is displayed in the coverage report.
    - Memory profiling for C and C++
    - Memory Profiling for Java
    - Performance profiling
    - Runtime tracing
    - Trace Probes for C
    - 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
  - Using the graphical user interface
  - Test script languages

Template instrumentation

Code Coverage for C++

Code Coverage performs the instrumentation of templates, functions, and methods of template classes, considering that all instances share their branches. The number of branches computed by the feature is independent of the number of instances for this template. All instances will cover the same once-defined branches in the template code.

Files containing template definitions implicitly included by the compiler (no specific compilation command is required for such source files) are also instrumented by the Code Coverage feature and present in the instrumented files where they are needed.

For some compilers, you must specifically take care of certain templates (for example, static or external linkage). You must verify if your Code Coverage Runtime installation contains a file named templates.txt and, if it does, read that file carefully.

To instrument an application based upon Rogue Wave libraries , you must use the -DRW_COMPILE_INSTANTIATE compilation flag that suppresses the implicit include mechanism in the header files. (Corresponding source files are so included by pre-processing.)
To instrument an application based upon ObjectSpace C++ Component Series , you must use the -DOS_NO_AUTO_INSTANTIATE compilation flag that suppresses the implicit include mechanism in the header files. (Corresponding source files are so included by pre-processing.)
Any method (even unused ones) of an instantiated template class is analyzed and instrumented by the Instrumentor. Some compilers do not try to analyze such unused methods. It is possible that some of these methods are not fully compliant with C++ standards. For example, a template class with a formal class template argument named T can contain a compare method that uses the == operator of the T class. If the C class used for T at instantiation time does not define an == operator, and if the compare method is never used, compilation succeeds but instrumentation fails. In such a situation, you can declare an == operator for the C class or use the -instantiationmode=used Instrumentor option.

Related Topics

Selecting coverage types | Code Coverage settings