Getting Started
Review your first run
Use run evidence to decide whether a failure is a regression, stale test, or environment issue.
Runs are the operating record for your regression process. Review them before rerunning, editing test cases, or escalating failures.
What to inspect
Start with the run status and result summary, then inspect:
- The test case or test plan that created the run.
- Trigger type, start time, completion time, and duration.
- Passed, failed, skipped, and completed test case counts.
- Failed reason and per-test-case run evidence.
- Screenshots, recordings, and step-level summaries when available.
Failure review
Classify the failure before taking action:
- Product regression: The expected behavior is broken in the tested environment.
- Stale instructions: The product changed, but the test case still describes the old UI.
- Bad test data: The account, workspace, or record state no longer matches the test.
- Environment issue: The target environment, third-party dependency, or deployment is unavailable.
Next action
Create or update an issue when the failure represents work your team should track. Edit the test case when the test is stale. Rerun only after you understand what changed or when the failure was clearly environmental.