ISTQB Game Testing Glossary

About this topic

Source: ISTQB Certified Tester Game Testing (CT-GaMe)

Game testing adds concerns that conventional software testing has no vocabulary for: whether the experience is enjoyable, whether the underlying mathematics pays out as designed, and whether a shared world stays consistent across many simultaneous players. These terms come from the ISTQB Game Testing syllabus.

The defining difference is that a game can be entirely defect-free and still fail, because the product's purpose is an experience rather than a function. Playtesting evaluates that experience directly — whether the game is fun, fair, and appropriately paced — and produces findings that no functional test suite would surface. Player perspective testing formalises this by testing from the position of a specific player type rather than a generic user.

Math testing verifies the numerical models underneath the game: drop rates, damage formulas, progression curves, and payout behaviour. In gambling and chance-based games this extends to par sheet testing, which validates the probability tables governing returns against their specification and, where applicable, against regulatory requirements. Errors here are commercially and legally serious in a way that a cosmetic bug is not.

Multiplayer testing addresses everything that only emerges when players interact: state synchronisation across clients, latency and its effects on fairness, matchmaking, and the failure modes of a shared persistent world. Audio testing verifies that sound behaves correctly relative to game state and player position, which is both a functional and an experiential concern.

What this topic covers

• Playtesting and player perspective
• Math and par sheet testing
• Multiplayer and synchronisation
• Audio testing
• Bug hunting
• Experience versus correctness