Playwright / Scenario
Green Dashboard, Repeated Customer Report
Use retry evidence to distinguish infrastructure noise from an intermittent product failure and set a policy that preserves the signal.
- Difficulty
- Hard
- Format
- Scenario
- Points
- 200
- Estimate
- 16 min
// MISSION BRIEF
Your Mission
A release dashboard is green, yet customers report the same intermittent cart failure seen on first attempts in CI. Inspect the configuration, retry history, trace evidence, and team policy. Decide how the suite should report and govern the defect.
// FIRST CONTACT
Battle teaser
First artifact
playwright.config.ts
How should the team classify the cart result based on the evidence?
- AAn assertion typo because the expected badge value is numeric text
- BAn intermittent product race; the retry pass does not disprove it
- CA browser installation error because the first attempt failed
- DTreat it as a harmless test flake because the retry passed, provided the team keeps the overall failure frequency low and continues counting flaky outcomes as green
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
playwright-retriesflaky-testsproduct-raceplaywright