Integration of Objects Under Test
Test RealTime - User Guide
Report Explorer
The Report Explorer displays each element of a Test Verdict report with a
Passed
or
Failed
symbol:
·
Elements marked as Failed are either a failed test, or an element that contains
at least one failed test.
·
Elements marked as Passed are either passed tests or elements that contain
only passed tests.
Test results are displayed in two parts:
·
TestClasses, TestSuites and derived test cases of all the executed JUnit scripts.
·
Class results for the entire Test.
Report Header
Each Test Verdict report contains a report header with:
·
The path and name of the .xrd report file.
·
A general verdict for the test campaign:
Passed
or
Failed
.
·
The number of test cases
Passed
and
Failed
. These statistics are calculated on
the actual number of test elements (Test Case, Procedure, Stub and Classes)
listed sections below.
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 TestSuite,
TestClass and derived test case encountered. In this section, statistics reflect the
number of times an element occurs in a JUnit script.
Test Results
For each test case, 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
assert
functions 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
188
