Overview
The tests view shows a summary of test results for a build. This view is meant to complement full HTML reports generated by testing tools, which can be captured as artifacts and browsed via the web interface. Test results will only appear in this view if detected during post-processing. For example, refer to the JUnit report post-processor.
Information Shown
The test view is split into two panes. The left ("navigation") pane shows a list of all stages executed in the build, with a count of tests (and any failed test). By clicking on a stage name, the test results for that stage will be display in the right ("detail") pane.
All test results for a stage are displayed in a single summary table. To see only failed tests, click the "hide successful" link. Test results are divided into "suites", which are collections of results (and may be nested), and "cases" which are individual test cases. The hierarchical relationship between suites and cases is illustrated by indenting the name of the result in the left column of the table.
suites
For each suite, the table will show:
- name: the name of the suite
- status: the result of the suite execution, which will be the worst result of any child suite or result
- details: a summary of the total number of children, and the total number with status error and failure
- time: if avilable, the time taken to execute the suite
cases
For each case, the table will show:
- name: the name of the case
- status: the result of the case execution
- details: if the case failed, an optional error/failure message
- time: if avilable, the time taken to execute the case
Statuses
Test results are displayed in the "status" column. Three different statuses are possible:
| Status |
Description |
| error |
The test failed in an unanticipated way, e.g. by throwing an exception. |
| failure |
The test failed in an anticipated way, e.g. by an assertion failure. |
| success |
The test completed successfully. |