Basic concepts of video and game testing
What this domain tests
You must explain how testing a game differs from testing business software, how games are built, who tests them, and which artefacts testers produce.
What is different about game testing
Game testing still applies ISTQB fundamentals, but adds quality attributes a business system does not have: fun, playability, immersion, difficulty balance and "game feel". A jump that triggers correctly and reaches the right height can still fail because it feels floaty. Games ship across many hardware configurations, so compatibility, performance and platform certification (Sony TRC, Microsoft XR, Nintendo lotcheck) are first-class concerns. Multiplayer, online services, monetisation and live operations add network, security and virtual-economy risks.
Lifecycle and gates
Typical stages run: concept, pre-production/prototype, production, alpha (feature complete), beta (content complete, polish and balance), gold/master (submission), post-release (patches, live ops). Test focus shifts with the stage: mechanics and tooling early; content, balance and compatibility later; regression and certification last.
Roles and testware
Test manager, test lead, test analyst, technical test analyst, game testers, and playtesters who are often not QA. Testware includes test strategy and plan, test cases, exploratory charters, defect reports, test summary reports and gameplay telemetry.
Worked example
At beta, players report the jump "feels floaty". It triggers, reaches the correct height and never crashes, so there is no functional defect. Reasoning: classify it as a playability/game-feel issue, a game-specific non-functional quality; assign it to a designer, then verify with a comparative playtest (A/B builds plus telemetry on airtime and input latency) rather than a pass/fail script.
Traps that cost marks
- Equating game testing with crash-hunting.
- Confusing alpha (features complete) with beta (content complete, polish).
- Using playtesters as a substitute for structured testing.
- Ignoring certification requirements until submission week.