To run the Component Testing Wizard from the Start Page
Graphical User Interface
2. The
Application Files page opens. Use the Add and Remove buttons to build a
list of source files and header files (for C and C++) to add to your project.
The Configuration Settings button allows you to override the default
Configuration Settings.
Select Compute Static Metrics to run the analysis of static testability metrics.
Click Next> to continue.
Note If the static metrics analysis takes too much time, you can clear the
Compute Static Metrics option. In this case, the calculation and display of
static metrics in any further steps are disabled.
Note With Component Testing for Ada, it is not possible to submit only an
Ada procedure file. Instead, you must include the single procedure in a
package.
3. The
Components Under Test page allows you to select the units or files for the
selected source files.
In order to help you choose which components you want to test, this page
displays the metrics for each file or unit (packages, classes or functions
depending on the language).
Select File Selection to choose files under test or Unit Selection to choose the
source code units that require testing. The selection mode toggles the static
metrics displayed between file metrics or unit metrics.
Note If the Unit Selection view seems incomplete, cancel the wizard, from the
Project menu, select Refresh File Information and restart the wizard. See
Refreshing the Asset Browser.
Click Metrics Diagram to select the units under test from a graph
representation.
Click Next> to continue or Generate to skip any further configuration and to use
default settings.
4. The
Test Script Generation Settings page allows you to specify the test node
generation options. The General settings specify how the wizard creates the test
node.
·
Test Name: Enter a name for the test node.
·
Test Mode: Disables or enables the test boundaries.
·
Typical Mode: No test boundaries are specified. This is the default setting. For
Java, all dependency classes are stubbed in the node.
·
Expert Mode: This mode allowing you to manually drive generation of the test
harness. This provides more flexibility in sophisticated software architectures.
·
Node Creation Mode: Selects how the test node is created:
307
