Defect Reporting, Tracking, and Triage
What this domain tests
This domain tests whether you can write a defect that developers can reproduce and fix, and prioritize it correctly with the team.
Core rules
- A report needs a concise title, build and version, platform, environment, preconditions, exact steps, expected versus actual behavior, reproducibility, severity, priority, and evidence such as video, logs, a dump, or a save file.
- Severity is impact on the game; priority is urgency for the business or schedule. They are not the same value.
- Lifecycle: new, triaged, assigned, fixed, verified, closed. Reopen when verification fails.
- Triage includes product, QA, and development deciding fix, defer, duplicate, or not a bug, with the rationale recorded.
- One defect per report; do not bundle unrelated issues.
Worked example
After patch 1.3, loading a save created in 1.2 crashes to desktop on PC. The title names the build, platform, and action. Severity is critical because it blocks progression; priority is high because it is a release blocker. Evidence includes the save file, crash dump, video, and five out of five reproductions. The reasoning: severity comes from player impact, priority comes from release risk, and both belong in the report.
Traps
Game broken titles; setting severity equal to priority; missing build or platform; no reproduction steps; attaching a screenshot without logs; closing a fix without retesting on the reported build; filing duplicates as separate known issues.