Add expiring quarantine entries with accountable owners
Quarantined tests have accumulated without owners or a return date.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- CI governance · Testing
Estimated field mix
- Quality engineering80%
- Platform engineering20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional web team reruns red builds until they pass. Shared clocks, leaked state, and unawaited work make failures hard to trust.
Setup prerequisites
- Create a small local application with three deliberately flaky tests using synthetic data and local endpoints.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BTEST-101 · Record first-attempt results separately from rerun results
- BTEST-102 · Reproduce order-dependent failures with a saved shuffle seed
- BTEST-103 · Trace leaked database rows between test cases
- BTEST-104 · Replace wall-clock races with explicit clock control
- BTEST-106 · Find async work that escapes test teardown
- BTEST-107 · Separate product defects from environmental test failures
Acceptance criteria
- Require owner, reason, linked reproduction, and expiry.
- Continue executing quarantined tests in a visible lane.
- Fail policy checks on expired or unmatched entries.
Implementation constraints
- Quarantine cannot remove coverage silently.
Verification to include
- Accept a complete short-lived entry.
- Reject expired, wildcard-only, and ownerless entries.
Deliverables
- Quarantine policy validator.
Rollout and recovery
Start with a reviewed inventory; restore tests automatically only after policy conditions are met.
Value of the work
For the engineer: Practice controlled diagnosis, isolation, and test reliability measurement.
For the team: Recover useful failure signals and reduce blind reruns without hiding product defects.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.