Arcade Game Maker Pedagogical Product Line: Brickles Test Report
Introduction
The Brickles product was tested according to the plan defined in the Brickles system test plan. The product passed all of the tests, and this report provides the results of the testing conducted on August 1, 2003.
Test Items
The basis for the tests are the use cases shown here. The Brickles game is a subset of the total functionality needed for the product line. The set of use cases that form the basis for the tests is shown in the diagram.
Brickles Use Cases
The following use cases apply to Brickles:
- AGM001 - Play game
- AGM002 - Exit game
- AGM006 - Play Brickles
- AGM009 - Initialization
- AGM010 - Animation loop
- AGM011 - Install game
- AGM012 - Uninstall game
- Change case - Save game
- Change case - Set speed of play
- Change case - Check previous best score
- Change case - Save score
For the full text of these use cases, refer to Arcade Game Maker Pedagogical Product Line: Requirements Model.
Testing Strategy and Approach
Syntax
The player interacts with the Brickles program using the mouse and the keyboard.
Description of Functionality
The functionality being tested is the basic Brickles game running in a simple Win32 environment.
Arguments for Tests
An analysis of scenarios in the use cases is depicted in the following table. Assign variables to values that can vary, and determine each variable's data type by examining specifications and the context. For each data type, define a set of equivalence classes. These classes are sets of values within the variable's data type for which product behavior is expected to be equivalent.
| Use Case Analysis | ||
| Variable | Data Type | Equivalence Classes |
| Left mouse button | boolean | Up, down, down & up |
| Mouse location | Point | Inside window, outside window |
| Number of pucks lost | int | 0, 0<numberOfPucksLost<3, 3 |
| Number of bricks remaining | int | 0, all, 0<brickCount<all |
Expected Output
As test cases are built, an oracle (usually a human) defines what constitutes a correct answer. The following table shows the expected results for each test case.
| Expected Output | |||||
| Test Case | Left Mouse Button | Mouse Location | Pucks Lost | Bricks Remaining | Expected Results |
| 1 | Down & up | Inside window | 0 | 0 | Won dialog |
| 2 | Down & up | Inside window | 1 | 0 | Won dialog |
| 3 | Down & up | Inside window | 2 | 0 | Won dialog |
| 4 | Down & up | Inside window | 3 | >0 and <all | Lost dialog |
| 5 | Down & up | Inside window | 3 | all | Lost dialog |
| 6 | Down | Outside window | Don't care | >0 | No effect |
| 7 | Down &
up and then down & up |
Inside window | 2 | 0 | Won dialog |
Observed Results
| Observed Results | ||
| Test Case | Expected Results | Observed Results |
| 1 | Won dialog | Passed |
| 2 | Won dialog | Passed |
| 3 | Won dialog | Passed |
| 4 | Lost dialog | Passed |
| 5 | Lost dialog | Passed |
| 6 | No effect | Passed |
| 7 | Won dialog | Passed |
