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
Runtime tracing
Advanced runtime tracing
Splitting trace files

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

Splitting trace files

Runtime Tracing for C and C++a

During execution, Runtime Tracing generates a .tdf dynamic file. When a large application is instrumented, the size of the .tdf file can impact performance of UML/SD Viewer.

Splitting trace files allows you to split the .tdf trace file into smaller files, resulting in faster display of the UML Sequence Diagram and to optimize memory usage. However, split trace files cannot be used simultaneously with On-the-Fly tracing.

When displaying split .tdf files, Runtime Tracing adds Synchronization elements to the UML sequence diagram to ensure that all instance lifelines are synchronized.

To set Split Trace mode:

In the Project Explorer, select the highest level node from which you want to activate split trace mode.
Click the Open Settings... button.
Select Runtime Analysis and the Runtime Tracing settings.

Select Trace Control.

Set the Size (Kb) of each split .tdf. The default size is 5000 Kb.

Specify a File Name Prefix for the split .tdf filenames. The prefix is followed by a 4-digit number that identifies each file.

Click OK.

Note The total size of split .tdf files is slightly larger than the size of a single .tdf file, because each file contains additional context information.