QABattle

Manual Testing / Scenario

Rewrite the Report That Got Bounced

A real bug, a terrible report, a developer who closed it in 40 seconds. Rebuild the report line by line until it becomes unbounceable.

Difficulty
Medium
Format
Scenario
Points
150
Estimate
14 min

// MISSION BRIEF

Your Mission

BUG-2291 describes a genuine defect, and it just came back marked 'Cannot Reproduce / Working as Intended'. The bug is real; the report killed itself. You have the original report and the tester's private session notes, which contain everything the report should have said.

Fix the advocacy failure. Decisions are weighted.

// FIRST CONTACT

Battle teaser

First artifact

BUG-2291 as filed

Why did the developer bounce a real bug in 40 seconds?

  1. AThe missing P1 label caused it to be skipped
  2. BDevelopers reflexively bounce all discount bugs
  3. CThe report is unexecutable: no concrete steps, no data, no environment, no observable expected/actual. 'Use a discount' works on THEIR happy path, so the report reads as false alarm plus shouting
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

bug-advocacybug-reportingmanual-testingcommunication