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.
Testing software components
Component Testing for C
Writing a Test Script
Advanced C Testing
Importing legacy component testing files

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
  - Testing software components
    - Component Testing for C
      - Integrated, simulated and additional files
      - Testing shared libraries
      - Writing a Test Script
        Test Script Structure
        Using native C statements
        Automatically updating a .ptu test script
        Testing variables
        Stub simulation
        Environments
        Advanced C Testing
        Test Script Compiler Macro Definitions
        Testing Long Types
        Testing Main Functions
        Testing Pointers against Pointer Structure Elements
        Testing a String Pointer as a Pointer
        Initializing Pointer Variables while Preserving the Pointed Value
        Importing legacy component testing files
        Link tests to Requirements
        Testing a function with an infinite loop
      - Creating a test plan from a PTU to generate an HTML report
        You can generate a test plan report from a PTU test script that you create but do not run. You can directly run the test plan to generate a test plan report in an HTML format.
      - Generating a test plan report from a customized template
        You can generate a test plan report from a test plan template that you customize. Before you run the test plan, you need to select the customized template it in the configuration properties so that it applies to your project.
      - Viewing Reports
      - Component testing for C++
    - Understanding Component Testing for C++ reports
    - Contract-Check sequence diagrams
    - Test Driver Sequence Diagrams
    - Component Testing for Ada
    - About System Testing for C
    - Agents and Virtual Testers
    - System Testing for C Test Scripts
    - Understanding System Testing for C Reports
  - 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

Importing legacy component testing files

Component Testing for C

The file format of ATTOL UniTest and HCL DevOps Test Embedded (Test Embedded) v2001A Component Testing for C and Ada is not compatible with the current file format used by Test Embedded.

This means that any .prj, .cmp, and .ses files created with pre-v2002 versions of the product must be imported and converted in order to be used in a current Test Embedded project.

The Import feature creates a new workspace with the updated Component Testing script files.

Note This problem only affects the Component Testing for C and Ada feature. You can use previous Component Testing for C++ and System Testing tests in your current projects without importing them.

From the File menu, select Import.
In the window Import V2001A Component Testing Files Into a New Workspace, select the Add... button and then select those V2001A Component Testing files that you wish to import. To import a complete UniTest or Test Embedded v2001A project, you must select all the .prj, .cmp, and .ses files from that project.
Click the OK button
In the window Name Workspace, type in a name for the new workspace and click OK.

Limitations

This feature imports the session, project and campaign data from the old version of Component Testing, including references to and from test scripts as well as tested and integrated source files.

After the importation, you must manually check and update the following items:

Target Deployment Port: Use the TDP Editor to reconfigure any custom ATTOL Target Package settings. The Target Deployment Guide contains advanced information about upgrading from an old Target Package.
Configuration Settings: The Import feature retrieves -D condition information and include directories. Check the General, Build and Component Testing for C tabs of the Configuration Settings dialog box to identify any other settings that need updating.
Service and Family parameters: These are not imported and require manual updating with the Tester Configuration function.

Related Topics

About Component Testing for C and Ada | Manually Creating a Test or Application Node | Tester Configuration | Migrating from v2001A Target Deployment Ports | Upgrading from v2001 target deployment ports