How-to Guide
Create a regression suite
Build a suite from library cases for repeat validation.
Objective
Build a suite from library cases for repeat validation.
Prerequisites
- Cases in library
Procedure
Select cases
Filter library for regression-critical cases.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Confirm organization and team context in the Console header before making changes.
Create suite
Name suite and define order.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Note project, run, or agent IDs if you may need support escalation.
Schedule or run
Execute on demand or via schedule.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
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 suite available for operational runs.
Was this page helpful?
