← All articles
Game dev · 10 min read

Game QA is more than playing: how we test games

Progression blockers, balance, performance budgets, platform matrices and bug reports that developers can act on. A look inside a structured game QA process.

Game testing has a reputation as “playing games for a living”. In reality it is one of the most demanding areas of QA: a game has physics, AI, networking, save systems, economies, dozens of devices and the hardest requirement of all, that it must be fun. Here is how we structure it.

1. Test plan per milestone

We plan testing per production milestone, because the goals change:

MilestoneQA focus
PrototypeIs the core loop working and readable? Crash-free basic flow
Vertical sliceOne level at release quality: controls, camera, UI, audio, performance
AlphaAll features in: functional coverage, progression, saves
BetaContent complete: balance, localisation, compatibility, soak tests
Release candidateRegression, platform requirements, day-one patch readiness

2. Functional and progression testing

The most critical class of game bugs are progression blockers: situations where the player can't continue. We check every quest and level against questions such as:

  • Can the player complete objectives in an unexpected order?
  • What if a key item is dropped, sold or destroyed?
  • What happens when the player dies during a cutscene or a scripted event?
  • Do save/load restore every flag, inventory item and NPC state correctly?
  • Can the player get stuck in geometry with no way out?

3. Breaking the world on purpose

Systematic destructive testing finds what normal play doesn't:

  1. Run along every wall and corner to find collision holes
  2. Spam inputs, combine abilities, pause on the frame of an attack
  3. Alt-tab, unplug the controller, lose the connection mid-match
  4. Fill the inventory, reach the max level, overflow currencies
  5. Change the system language, resolution and refresh rate mid-game

4. Balance and economy

Balance bugs are subtle: nothing crashes, but players quit. We combine telemetry, spreadsheets and play sessions: time to complete each level, death heat maps, resource income vs. spending per hour, win rates per weapon or class. We report balance issues with numbers and a recommendation, not just “too hard”.

5. Performance budgets

Performance is a feature. We agree on budgets per target device and test against them on real hardware, not only on the developers' powerful PCs.

Target frame rate by device tier (FPS)Low-end mobile30Mid-range60Console / PC60High-end PC120
Example budget table: frame rate targets agreed at the start of production.
  • Frame rate and frame-time spikes in heavy scenes
  • Loading times for the first launch and each level
  • Memory usage and leaks over long sessions (soak tests of several hours)
  • Battery drain and heating on mobile devices
  • Network: latency, packet loss and reconnects in multiplayer

6. Compatibility matrix

PlatformWhat we cover
PCLow / mid / high GPUs, different drivers, ultrawide and 4K screens, keyboard + gamepads
MobileOld and new Android devices, popular iPhones, notches, small screens, low memory
ConsolesPlatform requirements (suspend/resume, accounts, trophies/achievements, storage full)
WebBrowsers, WebGL support, tab switching, mobile browsers

7. Game bug reports

A great game bug report includes the build number, platform, exact location (level, coordinates or a screenshot with minimap), the save file, and a video. Many engines let you attach a reproduction save or a console command; that turns a two-hour hunt into a five-minute fix.

We apply this exact process to our own game, Worldeath, and offer it to studios as standalone QA or as part of co-development.