How-to Guide
Quarantine a flaky test
Isolate unstable cases via Test Health quarantine workflow.
Objective
Isolate unstable cases via Test Health quarantine workflow.
Prerequisites
- Flaky test identified in Test Health
Procedure
Open Test Health
Quality → Test Health → flakiness or quarantine tab.
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.
Select flaky case
Review failure pattern and frequency.
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.
Quarantine
Apply quarantine per team policy.
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
Flaky case excluded from release gates until stabilized.
Was this page helpful?