Selenium / Scenario
Boss Fight: The Nightly That Cried Wolf
One suite, five compounding failures: mixed waits, a static driver under parallel methods, @CacheLookup staleness, an unsized headless viewport, and retry-to-green rot. Untangle all of it.
- Difficulty
- Boss
- Format
- Scenario
- Points
- 300
- Estimate
- 20 min
// MISSION BRIEF
Your Mission
You are the new automation lead. The gift waiting on your desk: a 420-test nightly with 27% failures, a retry wrapper hiding half of them, and a framework where every anti-pattern from the Selenium field manual coexists peacefully.
This is the boss fight: multiple root causes interlock, and fixing them in the wrong order wastes the week. Read all four artifacts before deciding anything. Decisions are heavily weighted.
// FIRST CONTACT
Battle teaser
First artifact
FrameworkCore.java (the crime scene)
Map failure signatures to framework lines. The 34% 'wrong page / command collision' cluster traces to:
- A[3]: the implicit wait is too long
- B[6]: retries corrupt the session
- C[1]+[5]: one static WebDriver shared by 8 parallel threads, every thread drives the same browser; ThreadLocal (or per-test) drivers are the fix
// SKILL TAGS