I85PREP
⌘ K
KDU CGT study materials
KDU CGT study resources

KDU CGT: Defect Reporting, Tracking, and Bug Life Cycle

KDU CGT · Work through your exam, one topic at a time.

All guide sections

Defect Reporting, Tracking, and Bug Life Cycle

What this domain tests

This domain covers writing a defect that an engineer can act on, and moving it through a defined life cycle without losing information. Expect severity versus priority, states and transitions, triage, verification and reopening.

Core rules

  • A strong report has a specific title, build and environment, preconditions, minimal reproduction steps, expected versus actual result, reproducibility (for example 5/5), severity, priority, and logs, video or save files.
  • One defect per report. Two symptoms may share a cause, but bundling them hides one when the other is fixed.
  • Severity is impact: crash, progression block, data loss, major, minor, cosmetic. Priority is scheduling order and can differ; a cosmetic logo error on the title screen may be high priority before a press event.
  • Typical states: New, Triaged, Assigned, In Progress, Fixed, Ready for Test, Verified, Closed, with Reopened, Deferred, Duplicate, Not a Bug and Cannot Reproduce as terminal or side states.
  • Verification means retesting the original steps on the fixed build, then running related regression. A fix can break neighbours.
  • 'Cannot reproduce' needs the environment, frequency and any differences from the reporter's setup.

Worked example

After patch 1.2, loading a save created in 1.1 crashes on the title screen, 10 out of 10 attempts, blocking all progression. Severity is critical because it is a crash plus save-data access loss; priority is P1 because it blocks the milestone. The report includes the save file, console firmware and the exact menu path. The fix ships in 1.2.1; the tester verifies the original save, a new save, a cloud save and a save from two versions back, then reopens if any variant still fails.

Traps

Confusing severity with priority. Vague titles such as 'game broken'. Missing build number. Multiple bugs in one ticket. Closing a fix without retesting. Failing to reopen when the bug returns. Filing 'cannot reproduce' without environment details. Arguing in the ticket instead of recording evidence.