Game Development Reference
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.
1. What is Rule 2?
2. Identify each of the following as Judger (J) or Perceiver (P) behaviors:
a. Noticed a misspelling in the user manual
b. Created a character with all skills set to 0 just to see what would happen
c. Reported that the AK-47 doesn't fire at the correct rate
d. Found a way to get his skater off the map
3. Which of the following is an appropriately detailed defect title?
a. Game crashes
b. Found a bug in multiplayer mode
c. Can't drive Fastkat vehicle into the hallway south of the main chamber
d. Character dies unexpectedly
4. Which of the following should be in the defect description?
a. Where the defect happened
b. How the defect happened
c. Who in the game caused the problem
d. What the defect did to the game
e. All of the above