background image
<< Splitting the Result File | Associating Test Nodes to Test Cases >>
<< Splitting the Result File | Associating Test Nodes to Test Cases >>

Working with Rational TestManager

Test RealTime - User Guide
Check that no warning message appears during instrumentation. It may be
necessary to exclude one or several components from instrumentation (attolcc -
exunit). See the Reference Manual for further information about
Instrumentation Launcher command line options.
Missing Results
Files are missing when the Test RealTime is launched to display report files. Code
Coverage results are missing or display the entire application as uncovered.
The runtime analysis trace dump was interrupted. Dumps can take a long time,
especially when the Memory Profiling feature is in use. See Generating SCI
Dumps for more information.
Missing files on another component:
The plug-in offers to display all the results for enabled components.
Disable the any components that are not under analysis.
No coverage results on a diagram
Check that the component was correctly generated with the Code Coverage
instrumentation option.
Check that the component is enabled for instrumentation. The Plug-in only
changes state diagrams for enabled components.
Check that the component is not read-only, such as for an inherited diagram.
Working with Rational TestManager
Rational TestManager is used to manage all aspects of testing and all sources of
information related to the testing effort throughout all phases of the software
development project.
Test RealTime integration with TestManager enables the following features:
Association of TestManager test inputs, via test cases, with Test RealTime test
nodes and Group nodes.
Execution of Test RealTime tests from within TestManager
Local copy of Test RealTime test and runtime analysis results, test scripts, and
referenced source code in the Rational project log folder, all of which can be
baselined along with other Rational project log files
Test RealTime test and runtime analysis results available within the Test
RealTime GUI directly from a LogViewer test log
342