Understanding Component Testing for C++ reports

Component Testing for C++

Test reports for Component Testing for C++ are displayed in OneTest Embedded's Report Viewer.

The test report is a hierarchical summary report of the execution of a test node. Parts of the report that have Passed are displayed in green. Failed tests are shown in red.

Report Explorer

The Report Explorer displays each element of a Test Verdict report with a Passed , Failed or Undefined symbol:

Test results are displayed in two parts:

Report Header

Each Test Verdict report contains a report header with:

Note   The total number counts the actual test elements, not the number of times each element was executed. For instance, if a test case is run 5 times, of which 2 runs have failed, it will be counted as one Failed test case.

Test Script

Each script is displayed with a metrics table containing the number of Test Suite, Test Class, Test Case, Epilogue, Procedure, Prologue and Stub blocks encountered. In this section, statistics reflect the number of times an element occurs in a C++ Test script.

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:

The displayed table gives the number of times a violation has occurred for each state. The status of this table is always Failed.

Related Topics

Understanding Component Testing for C++ UML Sequence DiagramsUsing the Report ViewerOpening a report  | Exporting reports