ISTQB CT-GaMe study plan

Define the scope of game testing by distinguishing functional, non-functional and platform certification testing with two original examples each

Explain how game architecture (engine, render loop, physics, asset pipeline) shapes testability and where defects typically originate

Compare video game testing with classic business-IT testing on release cadence, build volatility and patch economics

Identify test levels and test types applicable to games and map them to a sample project's backlog items

Classify game quality characteristics (performance, usability, fun/playability, compatibility, security) and state how each is verified

Derive risk items from a game concept by applying likelihood and impact scoring

Write risk-based test objectives that tie each risk to an observable exit condition

Distinguish product risk from project risk in a game production context

Select test approaches (exploratory, scenario, model-based, combinatorial, crowd) that fit specific game risks and justify each choice

Estimate test effort for a game milestone using a documented, repeatable technique

Define measurable entry and exit criteria for a playtest cycle

Translate platform certification requirements into prioritised test conditions

Design test cases from a game design document using equivalence partitioning and boundary value analysis on player stats and economy values

Build a state-transition model for a menu/save-load flow and derive coverage-based test cases

Apply decision tables to combat or loot rules with interacting conditions

Trace each designed test case back to a risk or requirement identifier

Implement a test environment checklist covering hardware tiers, OS versions, storefront builds and network conditions

Write reproducible defect reports for game-specific failures such as frame drops, desync and save corruption

Plan and execute a scripted regression pass after a simulated build change

Define test data and telemetry sources needed for verification and reporting

Design gameplay-mechanics tests for collision, hitboxes, difficulty curves and economy balance

Design graphics tests for frame rate, resolution scaling, texture quality and rendering artifacts

Design audio tests for mixing levels, spatialisation, latency and missing or looping assets

Design localisation tests for text expansion, font coverage, right-to-left layouts and culture-specific content

Evaluate categories of game testing tools (automation frameworks, performance profilers, capture/comparison tools, audio analysers, localisation checkers) against stated selection criteria

Match each identified risk to a candidate tool or a justified manual alternative

Assess automation feasibility for a game feature and state what should remain manual

Execute a small exploratory session with a documented charter and timebox

Consolidate all four domains into a single revision sheet of key concepts and technique triggers

Complete timed practice questions per domain and analyse every error by root cause

Re-derive risk-based test objectives and exit criteria for a new scenario under time pressure

State the exam's domain weightings and allocate remaining study time accordingly