QABattle

CI/CD & DevOps / Scenario

Quarantine Protocol

Main is red 12% of the time, devs mash re-run, and someone proposed 'retry everything 3x'. Design a quarantine policy that actually works.

Difficulty
Hard
Format
Scenario
Points
200
Estimate
15 min

// MISSION BRIEF

Your Mission

The org's trust in CI is bleeding out. You have the incident report, a sample flake, and a half-baked policy draft. Decide what a real quarantine process looks like: entry, exit, and the failure modes that turn quarantine into a graveyard.

Scoring: weighted decisions; the definition of quarantine counts double.

// FIRST CONTACT

Battle teaser

First artifact

State of CI (last 30 days)

What IS a test quarantine, done right?

  1. AKnown-flaky tests are removed from the merge-blocking gate but STILL RUN and are tracked, each with an owner and a deadline
  2. BFlaky tests are deleted; unreliable coverage is worthless
  3. CA separate repo where old tests are archived
  4. DFlaky tests are skipped entirely until someone remembers them
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

ci-cdflaky-testsquarantinetest-strategy