Bug reporting best practices
We have learned now about what should be included in a good bug report and how it should be structured. While every gaming studio might have different production practices, there are certain bug-reporting practices that can be implemented in any game team. Let’s look into them more closely.
Reliability
The bug report should be factual and present the real issue as it happened, without embellishment or additions. While it’s incredibly useful to add additional information and supporting documentation and files, such as screenshots, QA should restrain from presenting opinions as facts. Bug reports have a commentary field where QA can express their opinion on the bug, but as such: an opinion. Presenting it as a fact might cause a lack of trust in QA, throw the coder on the wrong track, and, in return, can affect bug-fixing rates and timelines. When we report bugs, we want to make sure that developers and other stakeholders reading bugs can...