Home
Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL DevOps Test Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
Testing with DevOps Test Embedded for Eclipse IDE
Read these topics to learn how to use the product.
Analyzing source code
Code coverage
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.

Test Execution Specialist Guide
This guide describes tasks that you can perform to test application code in HCL DevOps Test Embedded for Eclipse IDE. This guide is intended for testers or test execution specialists.
- Testing with DevOps Test Embedded for Eclipse IDE
  Read these topics to learn how to use the product.
  - Getting started with DevOps Test Embedded for Eclipse IDE
    HCL DevOps Test Embedded for Eclipse IDE (Test 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 DevOps Test Embedded (Test Embedded) workspace.
  - Importing DevOps Test Embedded examples
    Test 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.
    - Running static analysis
      You can use the Run Static Analysis menu in project explorer to analyze the application with static analysis tools such as Code Review and Static Metrics without running the application.
    - Estimating Instrumentation Overhead
    - Reducing Instrumentation Overhead
    - Code coverage
      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.
      - 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.
      - Coverage levels
        The product provides coverage information for various levels of statements, decisions, loops, calls, conditions.
      - Justification of non-covered lines of code
      - Changing code coverage settings
        You can edit the configuration settings for code coverage to explicitly include or exclude files, change the information mode, coverage level, and other settings.
      - Code coverage for assembler source files
        Assembler code coverage is essential primarily because embedded software often cannot be entirely written in high-level languages. In many projects, manually written assembler code are required for two main reasons
      - Using the Code Coverage Viewer to view reports
    - Memory profiling
      Memory profiling is the process of analyzing a program's memory usage to identify and address issues related to memory consumption and management. Memory profiling help to understand how a program utilizes memory, detect memory leaks, and optimize resource usage.
    - Performance profiling overview
      The performance profiling tool provides performance data for each software component so that you can locate the performance bottlenecks.
    - Runtime tracing overview
      Runtime Tracing is a feature for monitoring real time interaction of your code in a dynamic UML sequence diagram. Runtime tracing uses source code instrumentation to generate trace data, which produces a UML sequence diagram.
    - Static metrics overview
      Statistical measurement of source code properties is an extremely important matter when you are planning your test work for a software project. HCL DevOps Test Embedded (Test Embedded) provides a static metrics report, which displays complexity data and statistics for your source code.
    - Code review
      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 DevOps Test Embedded (Test Embedded) provides an automated code review tool, which reports adherence to guidelines for your C source code.
  - 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
    Component testing provides a unique, fully automated, and proven solution for applications written in C/C ++, dramatically increasing test productivity.
  - Application monitoring
    With HCL DevOps Test Embedded for Eclipse IDE (Test Embedded for Eclipse IDE) you can monitor the global variables of cyclic executive applications and apply user actions.
- DevOps Test Embedded Studio Overview
  HCL DevOps Test Embedded Studio (Test Embedded Studio) is the classic user interface that supports C, C++, Ada test and analysis tools.

Code coverage

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.