QABattle

Test Automation / Quiz

Waits: The Physics of Flake

Fixed sleeps, condition waits, and polling: the synchronization physics that decide whether any UI suite, in any framework, can be trusted.

Difficulty
Easy
Format
Quiz
Points
100
Estimate
9 min

// MISSION BRIEF

Your Mission

Every UI automation framework ever built has the same core problem: the test moves at CPU speed, the app moves at network speed. How you bridge that gap decides your flake rate before a single locator is written.

This quiz is framework-agnostic: the principles apply to Playwright, Selenium, Cypress, Appium, and whatever ships next year.

Speed bonus active.

// FIRST CONTACT

Battle teaser

The structural flaw of sleep(3000) as a synchronization tool:

  1. ASleeps leak memory in most frameworks
  2. BThree seconds is too short, five is the standard
  3. CIt is wrong in both directions at once: pure waste when the app is faster, guaranteed failure when the app is slower
  4. DNothing, sleeps are fine if consistently sized
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

test-automationwaitsflakinesssynchronizatione2e-testing