Game Testing All in One (Game Development Series)

Use your knowledge of your Judger/Perceiver traits to get better at finding a wider variety of defects and get more testing done. This includes reading and thoroughly knowing the rules of the game. At the same time, take on positions , assignments, or roles that make the most out of your tendencies.

Once you've seen a bug, identify it, try to make it show up in more places, and try to make it show up more frequently. Then you're ready to document the bug in the defect tracking system. Use a specific title and provide a detailed description. Include files that provide evidence of the problem and could help reproduce and track down the defect. A poorly documented bug costs CCB time, developer time, and your time in reprocessing the same defect instead of moving on to find more bugs .

When you do your testing, have the tape running, so to speak, so that when the defect happens you have all the evidence to include in the bug report.

Expect to spend a portion of your time writing up defects, reporting your results, and going back over your issues with developers and re-running your tests on one or two experimental builds before a good fix makes it into a general release to the team.