Test quarantine
Test quarantine moves a flaky test out of the blocking suite into a tagged 'quarantine' suite that runs but doesn't fail the build. Quarantine prevents the flaky test from blocking deploys while preserving its signal for triage; the discipline requires actively working through the quarantine, not letting it grow.
Quarantine is a triage tool, not a permanent home. Healthy use: a test moves to quarantine when flakiness is identified; an owner is assigned; a deadline (typically 1-2 weeks) is set for fix or delete. Tests that linger in quarantine for months should be deleted. They're not catching regressions, they're not being maintained, and they're not going to be fixed. The metric to watch is quarantine size and age: a quarantine that's stable or shrinking is healthy; one that grows indicates teams aren't paying down the debt.