Component Testing for Ada Overview

Component Testing for Ada

Basically, Component Testing for Ada interacts with your source code through the Ada Test Script Language. The __TRT_PRODUCT_SHORTNAME__ Reference Manual contains full reference information on the Test Script Languages.

Testing with Component Testing for Ada is as simple as following these steps:

Component Testing for Ada supports Ada 83 and Ada 95.

How Component Testing for Ada Works

When a test node is executed, the Test Script Compiler (attolpreproADA) compiles both the test scripts and the source under test. This preprocessing creates a .tdc file. The resulting source code generates a test driver.

If any Runtime Analysis tools are associated with the test node, then the source code is also instrumented with the Instrumentor (attolada) tool.

The test driver, TDP, stubs and dependency files all make up the test harness.

The test harness interacts with the source code under test and produces test results. Test execution creates a .rio file.

The .tdc and .rio files are processed together the Component Testing Report Generator (attolpostpro). The output is the .xrd report file, which can be viewed and controlled in the OneTest Embedded GUI.

Of course, these steps are mostly transparent to the user when the test node is executed in the OneTest Embedded GUI.


To learn about


Source file types for code under test

Integrated, Simulated and Additional Files

Configuration Settings for Ada Component Testing test nodes

Initial and Expected Value Settings