Selenium / Scenario
Green Locally, Dead in Docker
The suite passes on every laptop and fails 31 tests in the headless CI container. Same code, same Chrome version. Hunt the headless-specific differences.
- Difficulty
- Medium
- Format
- Scenario
- Points
- 150
- Estimate
- 14 min
// MISSION BRIEF
Your Mission
Your team containerized the test suite. Locally (headed): 240/240 green. In CI (headless Chrome in Docker): 31 failures across click-intercepted errors, elements 'not interactable', and two visual checks. The versions match perfectly.
Work the evidence: CI log, the ChromeOptions, and a failure screenshot description. Decisions are weighted.
// FIRST CONTACT
Battle teaser
First artifact
DriverFactory.java
Root cause of the click-intercepted and not-interactable failures:
- ANo window size was set; headless Chrome defaults to a small viewport (800x600), which flipped the app into its mobile/responsive layout that the tests were never written for
- BHeadless Chrome cannot execute JavaScript-heavy pages
- CDocker networking is corrupting the DOM
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
seleniumheadlessdockerciresponsive