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 HCL OneTest™ Embedded for Eclipse IDE
Read these topics to learn how to use the product.
Analyzing source code
Enable runtime analysis tools
When the source code is run with any of the runtime analysis tools enabled, either alone or in a component test, the source code is instrumented and the results are displayed in a report.

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.
  - Getting started with HCL OneTest™ Embedded for Eclipse IDE
    HCL OneTest™ Embedded for Eclipse IDE is designed to integrate into your existing Eclipse-based tool chain. Use this section as a guide to a typical workflow for testing and evaluating your C source code in the Eclipse CDT environment.
  - Importing C projects
    You can either create a new C project with the Eclipse CDT tools or you can import your existing C source files or Eclipse projects into your HCL OneTest™ Embedded workspace.
  - Importing HCL OneTest™ Embedded examples
    HCL OneTest™ Embedded is provided with several sample projects to help you get started.
  - Analyzing source code
    - Runtime analysis overview
      The runtime analysis tools are designed to closely monitor the behavior of your application for debugging and validation purposes. These features use source code insertion to instrument the source code providing dynamic analysis of the application while it is running, either on a native or embedded target platform.
    - Enable runtime analysis tools
      When the source code is run with any of the runtime analysis tools enabled, either alone or in a component test, the source code is instrumented and the results are displayed in a report.
    - Running instrumented applications
      To run a program with runtime analysis tools enabled, you must run it as an instrumented application.
    - Estimating Instrumentation Overhead
    - Reducing Instrumentation Overhead
    - Code coverage
    - Memory profiling
    - Performance profiling
    - Runtime tracing
    - Installing the Recommended GNU Compiler on Windows
    - Static metrics
    - Code review
  - 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
  - Application monitoring
    With HCL OneTest™ Embedded for Eclipse IDE you can monitor the global variables of cyclic executive applications.
- Testing with Studio

Enable runtime analysis tools

When the source code is run with any of the runtime analysis tools enabled, either alone or in a component test, the source code is instrumented and the results are displayed in a report.

Before you begin

Before running a test with any of the runtime analysis tools enabled, ensure that the correct Target Deployment Port (TDP) is selected.

Procedure

To enable runtime analysis tools on your source code:

In the project explorer, right-click the project on which you want to enable the runtime analysis tools and click Properties.
Click C/C++ Build > Settings and select the Build TDP page to check that the correct TDP is selected.
If necessary, click the Target Deployment Port value to change the TDP.
Select the Build Instrument page and select Settings > General > Selective instrumentation.
Select the Build Options line and click Edit.
In the Build Options window, select the runtime analysis tools that you want to enable.
- Memory Profiling detects memory leaks and allocation problems.
- Performance Profiling locates performance issues and bottlenecks.
- Code Coverage provides coverage information of the source code as it is run.
- Runtime Tracing displays a dynamic UML sequence diagram of the run.
- Static Metrics evaluates the complexity of the source code.
- Code Review assesses compliance to coding rules.
- Debug enables the workbench debug mode.
Click OK, Apply the changes and close the Properties window.
Click Project > Clean > Clean all projects.
If the project is successfully built, in the project explorer, the Binaries folder contains the compiled binary executable for the project. If the project did not build successfully, see the Troubleshooting section for help on resolving compilation issues.