How-to Guide
Compare test runs
Perform regression analysis across two or more runs.
Objective
Perform regression analysis across two or more runs.
Prerequisites
- Two or more runs exist
Procedure
Open run comparison
Runs → Compare or select runs to compare.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm organization and team context in the Console header before making changes.
Select baseline and candidate
Choose runs for diff analysis.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Note project, run, or agent IDs if you may need support escalation.
Review differences
Identify new failures and fixed cases.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Regression impact identified between runs.
Was this page helpful?