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.
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.
Analyzing running applications
Code coverage
Coverage types
C coverage

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.
- 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.
  - 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.
  - 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
        Block coverage
        Call coverage
        Condition coverage
        Function coverage
        Additional statements
        C++ coverage
      - Using the Code Coverage Viewer to view reports
      - Coverage source report
      - Coverage rates report
      - On-the-fly code coverage
      - Code Coverage Dump Driver
      - 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.
      - Cleaning code coverage report files
      - Justification of non-covered lines of code
      - 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
    - 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.
    - Memory Profiling for Java
    - Performance Profiling
    - Viewing UML sequence diagrams
    - Advanced 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
  - Tests linked to requirements
    With HCL DevOps Test Embedded (Test Embedded), you can link a test case or a service to one or several requirements that come from another tool to create a traceability matrix between requirements and test results.
  - Test script languages

C coverage

C code coverage refers to the measurement and analysis of how much of the source code in a C program has been executed during testing. Code coverage is an essential aspect of software testing, providing insights into the thoroughness and effectiveness of the test suite.