QABattle

Manual Testing / Scenario

Release Night Triage

It's 9 PM, release is at midnight, and four bugs just landed in your queue. Choose what blocks, what ships, and what you tell the release manager.

Difficulty
Medium
Format
Scenario
Points
150
Estimate
12 min

// MISSION BRIEF

Your Mission

You're the QA lead for tonight's release of a food-delivery app. The release train leaves at midnight, three hours away. Four bugs just arrived in triage.

Read the bug queue artifact carefully, then make the calls a lead has to make: severity, priority, and what blocks the train.

Remember: severity = technical impact. Priority = business urgency. They are not the same axis, and tonight they will disagree.

// FIRST CONTACT

Battle teaser

First artifact

Tonight's Bug Queue

BUG-1201 (payment double-charge, ~10% repro on retry): what severity do you assign?

  1. AMajor, bad, but the retry path is uncommon
  2. BMinor, support can refund affected users manually
  3. CCritical, financial data corruption, even at 10% repro
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

triageseveritypriorityrelease-management