Cypress / Scenario
Boss Fight: The Friday Flake Storm
Four specs, four different flake signatures, one nightly pipeline nobody trusts anymore. Diagnose all four and rule on the retry policy. No pressure.
- Difficulty
- Boss
- Format
- Scenario
- Points
- 300
- Estimate
- 18 min
// MISSION BRIEF
Your Mission
It is Friday. The nightly run failed again, differently than Thursday. Management wants to 'just add retries'. You have the CI summary and the offending code.
This is the boss fight: four distinct flake archetypes hide in these artifacts. Name each root cause, pick each fix, and make the retries call like a lead. Decisions are weighted; wrong diagnoses cost the most.
// FIRST CONTACT
Battle teaser
First artifact
Nightly CI summary (last 5 runs)
checkout.cy.ts, toast assertion times out intermittently. Root cause and fix:
- AThe toast component needs a longer display duration
- BThe 2s sleep races the order POST; on slow nights the response lands later. Intercept the POST, cy.wait('@order'), then assert the toast
- CToasts are unreliable to test; assert on the URL instead
- DIncrease the sleep to 5000ms, the p99 of the endpoint
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
cypressflakecidebugging