Console

Results

Interpret validation outcomes and trends.

Overview

Results interpret case-level pass/fail, duration trends, and failure patterns within completed runs. Each result links to expected vs actual assertions, execution logs, screenshots, and traces where captured.

Use Results with Test Health for flakiness quarantine and Runs comparison for regression analysis across builds.

Step-by-step procedure

Open run Results tab

Operate → Runs → select run → Results.

Filter by status: failed, passed, skipped.

Drill into failed cases

Open case detail for expected vs actual.

Cross-link to logs and artifacts tabs.

Export or share

Export CSV for analytics pipelines.

Share run URL with reviewers (respect RBAC).

Key concepts

Passed: Case completed; all assertions satisfied within timeout.
Failed: Assertion mismatch, timeout, or environment error.
Skipped: Case excluded by filter, quarantine, or prerequisite failure.

Read the evidence behind a result

Confirm the test, source revision, inputs, environment, and execution time before comparing outcomes. A changed dependency or configuration can explain a difference even when the application code appears unchanged.

Distinguish assertion failure, execution error, skipped work, and incomplete evidence using the states documented for your service. When repeating a run, retain the previous outcome and explain what changed; a later pass does not erase the need to understand an intermittent failure.

Was this page helpful?