Component Testing for C
Test RealTime - User Guide
Component Testing for C
The Component Testing for C feature of Test RealTime provides a unique, fully
automated, and proven solution for applications written in C, dramatically increasing
test productivity.
How Component Testing for C Works
When a test node is executed, the Component Testing Test Compiler (attolpreproC)
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 features are associated with the test node, then the source
code is also instrumented with the Instrumentor (attolcc1) 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 Test RealTime GUI.
Of course, these steps are mostly transparent to the user when the test node is
executed in the Test RealTime GUI.
Component Testing for C Overview
Component Testing for C interacts with your source code through the C Test Script
Language. The Rational Test RealTime Reference Manual contains full reference
information about each of these languages.
Testing with Component Testing for C is as simple as following these steps:
·
Set up your test project in the GUI
·
Write a .ptu test script
·
Run your tests
·
View the results.
Upon execution, Component Testing compiles both the test scripts and the source
under test, then instruments the source code if necessary and generates a
test driver
.
The test driver, TDP, stubs and dependency files make up a
test harness
.
The test harness interacts with the source code under test and produces test results.
126
