Skip to main content

Test result statuses

Test Services reports outcome and progress at several levels: the overall run, each individual test, the live system state, and each progress step within a test. This page lists the status values shown at each level and what each one means. The values are the same on the home page, the progress view, the history list, and the Summary report.

Overall run result

The overall run result summarizes a whole verification run in a single value. It appears as the Last result on the home page and as the overall test result on the first page of the Summary report. A run produces Passed only when every executed test passes; a single failed, aborted, or unavailable test prevents an overall Passed.

Table: Overall run result values

ValueMeaning
PassedEvery executed test produced a passing result.
FailedAt least one test failed, was unavailable, or could not run.
Not availableNo tests have been executed yet.
AbortedA user stopped the run before it finished. The Summary report names the user who aborted it.

Individual test result

Each test shows its own result and the date and time of its last execution. The result is independent of the overall run result; a single test can pass while the run as a whole fails.

Table: Individual test result values

ValueMeaning
PassedThe test produced a passing result.
Passed with additional informationThe test passed, with additional information recorded in the report. In the test list it appears as Passed with an information icon (tooltip "Passed with additional information"), and as Passed in the Summary report grid.
FailedThe test produced a failing result.
Not availableThe test could not run and produced no report. A running or pending test that was aborted, or a test whose setup failed, shows this value.
(Blank)The test has not been executed yet, or it is unavailable or disabled on this machine.

System status

The system status reflects what the machine is doing as a whole. It appears at the top of the home page and governs whether tests can be started. While the status is Running, test selection is read-only and cannot be changed.

Table: System status values

ValueMeaning
ReadyNo tests are running. The system is idle and tests can be started.
RunningA test execution is in progress.
AbortingThe current run is being stopped. The status stays Aborting until the run finishes stopping, then returns to Ready.
Not availableNo available or enabled tests are on this machine, for example when no plug-ins are installed.

Per-test status during a run

While a run is in progress, each test in the run carries its own live status. These values describe where a test is in the execution lifecycle, not its final result.

Table: Per-test status values

ValueMeaning
PendingQueued, not yet started.
RunningExecution in progress.
CompletedAll steps finished.
FailedExecution finished with a failure.
AbortingA stop has been requested and is being applied to this test.
AbortedThe test was stopped before completion.

During a stop, a Running or Pending test moves through Aborting to Aborted, while a test that already reached Completed is unchanged.

Progress step status

A test execution is broken into steps, each shown in the progress view with its own status and start time. The progress header also shows a counter of completed steps against the total, in the form 4/10.

Table: Progress step status values

ValueMeaning
PendingThe step is queued but has not yet started.
In ProgressThe step has started but not yet finished.
CompletedThe step finished successfully.
FailedThe step started but could not finish because of an error. The step shows a descriptive error message.
SkippedThe step was bypassed because the test failed or was stopped before reaching it.
AbortedThe step at which a stop finished.

When a step fails, all previously executed steps remain visible, and the failed step shows its error message rather than disappearing from the view.

See also