Conceptually designing, implementing and executing game software tests
What this domain tests
The ISTQB test process applied to games: analysis, design, implementation, execution and completion.
Test conditions and design techniques
Derive test conditions from the test basis: game design documents, mechanic specifications, user stories, the risk register and platform requirements. Black-box techniques map well - equivalence partitioning and boundary value analysis for damage formulas, currency caps and level thresholds; decision tables for loot tables and ability rules; state transition testing for menus, quest states, save/load and AI behaviour; use case testing for player journeys. Experience-based techniques such as timeboxed exploratory charters, error guessing and checklists suit emergent gameplay. White-box coverage applies where code-level logic matters.
Implementation
Each test case needs preconditions, test data (prepared save files, accounts, debug or cheat consoles), environment (dev kits, GPU/OS matrix), expected result and priority. Procedures and suites organise execution, and traceability links tests back to conditions and risks.
Execution and completion
Run prioritised suites, record actual results, log defects with reproduction steps, build/version, platform, and both severity and priority. Then regression-test and report.
Worked example
A quest state model: NotStarted → Active → Complete, with transitions accept, abandon, complete and turn in. Using state transition testing at 0-switch coverage, write cases for every valid transition plus invalid ones such as turning in while still Active. Reasoning: invalid transitions are where progression blockers hide, and modelling them exposes the gaps before code exists.
Traps that cost marks
- Test cases written without an expected result.
- Confusing severity (impact) with priority (urgency).
- Treating exploratory testing as unstructured clicking.
- Not resetting save data between tests, which masks state-dependent bugs.
- Designing only positive paths for economy and progression logic.