QABattle

Manual Testing / Scenario

Three Days, Five Features, One Tester

The release cannot move and neither can the calendar. Allocate 24 testing hours across five features using risk, not fairness, and defend every hour out loud.

Difficulty
Hard
Format
Scenario
Points
200
Estimate
16 min

// MISSION BRIEF

Your Mission

Release is Friday. You have three days (roughly 24 focused hours) and five features of wildly different risk. Equal time per feature is the comfortable, indefensible default.

Build the risk-based plan: score, allocate, and, hardest of all, write the sentence that tells stakeholders what will NOT be tested. Decisions are weighted.

// FIRST CONTACT

Battle teaser

First artifact

The five features

Rank the features by risk (likelihood x impact), highest first:

  1. AF1, F3, F5, F2, F4, money+new+rushed tops revenue-critical new parser, refactors carry regression risk, cosmetics trail
  2. BAll equal; risk ranking is guesswork without production data
  3. CF3, F2, F1, F4, F5, enterprise visibility first, then user-facing looks
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

risk-based-testingtest-strategyprioritizationmanual-testing