Integrated, Simulated and Additional Files
Automated Testing
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.
Integrated, Simulated and Additional Files
When creating a Component Testing test node for Ada, the Component Testing
wizard offers the following options for specifying dependencies of the source code
under test:
·
Integrated files
·
Simulated files
·
Additional files
Integrated Files
This option provides a list of source files whose components are
integrated
into the
test program after linking.
The Component Testing wizard analyzes integrated files to extract any global
variables that are visible from outside. For each global variable the Parser creates a
default test which is added to an environment named after the file in the .ptu test
script.
Simulated Files
This option gives the Component Testing wizard a list of source files to simulate--or
stub--upon execution of the test.
A stub is a dummy software component designed to replace a component that the
code under test relies on, but cannot use for practicality or availability reasons. A
stub can simulate the response of the stubbed component.
The Component Testing parser analyzes the simulated files to extract the global
variables and functions that are visible from outside. For each file, a DEFINE STUB
block is generated in the .ptu test script.
By default, no simulation instructions are generated.
Additional Files
Additional files are merely dependency files that are added to the Component
Testing test node, but ignored by the source code parser. Additional files are
compiled with the rest of the test node but are not instrumented.
95
