Game Development Reference
In its simplest form, a test suite is a series of incremental steps that the tester can per-
form sequentially. Subsequent chapters in this topic discuss in depth the skillful
design of test cases and suites through such methods as combinatorial tables and test
flow diagrams. For the purposes of this discussion, consider a short test suite you
would execute on Minesweeper , a simple game available with most versions of
Microsoft Windows. A portion of this suite is shown in Figure 8.4. You will find a sample
test suite in Appendix E.
Figure 8.4 Portion of a test suite for Minesweeper.
This is a very small portion of a very simple test suite for a very small and simple
game. The first section (steps one through seven) tests launching the game, ensuring
that the default display is correct, and exiting. Each step either gives the tester an incre-
mental instruction or asks the tester a simple question. Ideally, these questions are
binary and unambiguous. The tester performs each test case and records the result.
Because the testers will inevitably observe results that the test designer hadn't planned
for, the Notes field allows the tester to elaborate on a Yes/No answer, if necessary. The
lead or primary who receives the completed test suite can then scan the Notes field
and make adjustments to the test suite as needed for the next build.
Where possible, the questions in the test suite should be written in such a way that a
“yes�? answer indicates a “pass�? condition—the software is working as designed and no
defect is observed. “No�? answers, in turn, indicate that there is a problem and a defect