QABattle

Test Automation / Quiz

Flake Forensics

Non-determinism taxonomy, retries that confess, quarantine with teeth, and the metrics that tell you whether trust in the suite is rising or rotting.

Difficulty
Medium
Format
Quiz
Points
150
Estimate
10 min

// MISSION BRIEF

Your Mission

A flaky test is worse than a missing one: it burns CI minutes, trains engineers to ignore red, and hides real regressions in its noise. Fighting flake is a discipline with a method, not a mood.

This quiz covers the forensics: root-cause taxonomy, honest retry policy, quarantine mechanics, and the numbers that keep a suite trustworthy. Framework-agnostic by design.

Speed bonus active.

// FIRST CONTACT

Battle teaser

The defining property of a flaky test:

  1. ASame code, same configuration, different outcomes across runs, non-determinism somewhere in test, app, or environment
  2. BIt takes longer than 30 seconds
  3. CIt fails only on one engineer's machine
  4. DIt fails more than once per week
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

test-automationflakinessci-cdtest-strategye2e-testing