Game Development Reference
Figure 6.5 Game test phase containment data.
Figure 6.6 Game test phase containment graph.
Remember, this is not a measure of how well the executed tests perform. This is a measure
of how well faults were captured in the test designs, scripts, and/or code. Any mistakes
made in one of these activities will need to be repaired when they are eventually dis-
covered. Test mistakes that don't get discovered could impact the quality of the game
itself. A missing test, or a test that checks for the wrong result and passes, can send
game bugs on their merry way to the paying public.
As with the sigma value, look for ways to improve your PCE. If you had 100% con-
tainment in all of your phases, you would only have to run each test once and they
would all pass. Your customers wouldn't find any problems and you'd never have to
issue a patch. Think of the time and money that would save! Since the PCE is a function
of the faults produced and the faults, you can attack a low PCE at both ends.
Programmers can improve their ability to prevent the introduction of faults. Testers
and QA can improve their ability to detect faults.