Bug Tracking

A game project produces thousands of reports, and their value depends entirely on how they are written. Exact steps, build number, platform, expected and actual behaviour, and an attachment that shows the problem turn a note into a task a developer can close.

Triage is the second half: severity and priority have to mean something after the database has grown, duplicates must be merged, and regressions need to be visible as such. Jira and similar systems are the usual tools, often tied into the build system so that a fix can be traced to a version.

The skill belongs to QA, but it is expected well beyond it. Designers, artists and programmers all file reports, and a team in which everyone writes a reproducible one loses far less time than a team in which only the testers do.