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
Code review
Using a customized Naming script file
In HCL OneTest™ Embedded for Eclipse IDE, 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.

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
      - Code review overview
        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 adherence to guidelines for your C source code.
      - Configuring code review rules
        The code review tool uses a set of predefined rules. You can select the default rule configuration file for the code review tool. MISRA 2004 and MISRA 2012 from HCL OneTest™ Embedded V8.2.0 are the default installed rule configuration files. You can disable or set the severity level to Warning. You can also configure the entry-point option if your application is multi-threaded.
      - Using a customized Naming script file
        In HCL OneTest™ Embedded for Eclipse IDE, 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.
      - 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.
      - Executing the code review
        You can use the code review tool on any test, application node, or a single source file. The code review tool is run on the source code whenever you build the file.
      - 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.
  - 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

Using a customized Naming script file

In HCL OneTest™ Embedded for Eclipse IDE, 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.

To set the path to a customized Naming script file:

From the Project Explorer view, select the project node.
Right-click and select Properties.
In the window that opens, select Settings in the left panel.
In the right panel, click Settings > Code Review.
Click in Value cell of the Naming script file option and click ....
Select the sample file that you installed: Example “NamingRules1.pl".
Click Apply.