Game Development Reference
assigned to the defects they find. This approach turns testing into a game for the
testers to play while they're testing games. Did you follow that? Figure 9.10 shows what
a Star Chart looks like prior to adding the testers' stars.
Figure 9.10 Empty Star Chart.
If you're worried about testers getting into battles over defects and not finishing their
assigned tests fast enough, you can create a composite measure of each tester's contri-
bution to test execution and defects found. Add up the total number of test defects
found and calculate a percentage for each tester based on how many they found divided
by the project total. Then do the same for tests run. You can add these two numbers
for each tester. Whoever has the highest total is the “Best Tester�? for the project. This
may or may not turn out to be the same person who becomes the Testing Star.
Here's how this works for testers B, C, D, K, and Z for the Dev1 release:
Tester B executed 151 of the team's 570 Dev1 tests. This comes out to 26.5%. B has
also found 9 of the 34 Dev1 defects, which is also 26.5%. B's composite rating is 53.
Tester C ran 71 of the 570 tests, which is 12.5%. C found 7 out of the 34 total
defects in Dev1, which is 20.5%. C's rating is 33.
Tester D ran 79 tests, which is approximately 14% of the total. D also found 6
defects, which is about 17.5% of the total. D gets a rating of 31.5.