Mobile Testing / Scenario
Boss Fight: Device Lab Meltdown
Release day. Twelve devices, seven failures, one very calm QA lead required. Cluster the wreckage, find the four root causes, and decide what actually blocks the ship.
- Difficulty
- Boss
- Format
- Scenario
- Points
- 300
- Estimate
- 18 min
// MISSION BRIEF
Your Mission
The release-candidate run just finished across the full device matrix and the dashboard looks like a crime scene. Seven failures, but how many BUGS? Product wants a ship/no-ship call in an hour.
This is the boss fight: cluster failures by root cause, separate app bugs from test bugs from infra noise, and make the release call with reasons. Decisions are weighted; the clustering and the ship call weigh the most.
// FIRST CONTACT
Battle teaser
First artifact
Release-candidate matrix results
Seven failures. How many distinct root causes, and what are they?
- ATwo: Android is broken and iOS is fine
- BFour: the API 33+ notification-permission dialog (4 devices), an OOM app bug on low RAM (1), an ambiguous test locator on tablet layout (1), and infra noise, the offline Redmi (1)
- COne; the app is broadly broken and the run is unshippable evidence
- DSeven; each failing device is its own investigation
// SKILL TAGS