Tested Classes
Test RealTime - User Guide
Test Results
For each Test Case, Procedure and Stub, this section presents a summary table of the
test status. The table contains the number of times each verification was executed,
failed and passed.
For instance, if a Test Case containing three CHECK statements is run twice, the
reported number of executions will be six, the number of failed verifications will be
two, and the number of passed verifications will be four.
The general status is calculated as follows:
Condition
Result
Status
A verification fails
Failed
A verification does not occur
Undefined
All verifications pass on each execution
Passed
Tested Classes
Class results are grouped at the end of the report and sorted in alphabetical order.
For each class the report shows the general status of assertions (WRAP statement),
invariants, states and transitions.
The general status is computed as follows:
Condition
Result
Status
An assertion or invariant fails
Failed
An assertion or invariant does not occur
Undefined
All assertions or all invariants pass on each execution
Passed
A state is not reached
Not reached
A state has no exit transition
Not fired
When a class does not behave as expected, a table of violations is displayed. A
violation is observed at the exit of a state and can be one of the following:
·
Multiple: means that several states were reachable at the same time,
·
Illegal: means that no state was reachable.
The displayed table gives the number of times a violation has occurred for each state.
The status of this table is always Failed.
Understanding Component Testing for C++ UML Sequence
170
