Test Specification

Types of testing:

##Unit tests Black box variant probably useful for testing requirements
We will design a test level that will allow us to test each of the game play requirements in order. If we can beat the level, then each of these requirements is met (except death). If automation possible on Android device, create a script that will play through the test level.

• G1.1 - User controlled player - Inherent in G1.2
• G1.2 - Player can move left/right and jump - Simple puzzle that requires jump to the right, jump to the left
• G1.3 - Blocks that change gravity in all four directions - Path stops, gravity block up allows player to continue
• G1.4 - Blocks that break when shot with gun - Tested with G1.11
• G1.5 - Obtainable keys that unlock specific blocks - Key right before locked block, which is part of a wall
• G1.6 - Spikes that hurt/kill player - Automated? See below
• G1.7 - Blocks that lock screen - Tested with G1.8
• G1.8 - When screen is locked, player jumps from one side of lock to the other - Require locking and screen jumping in all 4 directions
• G1.9 - When player dies, he starts at beginning of level - With G1.6
• G1.10 - Player can finish level - Finish criteria
• G1.11 - Working gun - Wall of breakable blocks

Also negative testing:
Gun doesn't break all blocks, just the breakable ones - shoot unbreakables and try to go through, and if the script still finishes the level, it worked.

Link to possible unit test level

##Functionality tests

##Compatibility tests Does it work on all Android devices? Use emulator like Genymotion to allow testing of different types and versions of devices. Try single automated script on all, with allowed modification in case of strange differences.

##Soak tests Leave game running for hours on the start screen, in a level not moving, in a level holding a key, in a level jumping, in a level continually dying

Automated tests: Can we use testing frameworks to play the game?