ThisCalculator

Everyday

Indie Game QA Checklist: What to Test Before Release

Updated · Standard formula, shown below

This checklist covers the essential quality assurance tests every indie developer should run before releasing a game, from core functionality to platform-specific compliance. It outlines what to test, why it matters, and how to prioritize your limited time and budget.

Why a QA Checklist Matters for Indie Games

Indie developers often wear every hat, including QA. A single bad bug can sink a launch, generating negative reviews that are hard to recover from. A structured checklist ensures you catch the most impactful issues before players do, protecting your reputation and your revenue. It also helps you track what you’ve tested, so you don’t waste time re-checking the same areas while missing others.

Core Gameplay and Mechanics

This is the heart of your game. If the core loop is broken, nothing else matters. Test every mechanic in isolation and in combination with others.

  • Movement and controls: Walk, run, jump, crouch, climb, swim, drive, or fly. Test on all supported input devices (keyboard/mouse, gamepad, touch). Check for input lag, stuck states, and unresponsive buttons.
  • Combat and abilities: If your game has combat, test every attack, skill, spell, or ability. Verify damage numbers, cooldowns, resource costs, and visual/audio feedback. Test against different enemy types and in various environments.
  • Physics and collision: Check for objects falling through floors, getting stuck in walls, or launching unexpectedly. Test physics-heavy puzzles and environmental interactions.
  • Progression and save system: Play through the entire game from start to finish. Verify that quests, levels, or story chapters trigger correctly. Test saving and loading at every point, including mid-level and during cutscenes. Corrupted save files are a game-killer.

UI/UX and Menus

Players interact with your game through its interface. A confusing or broken UI frustrates users and can make them quit.

  • Main menu: New game, continue, load, options, and quit all work. Verify that the correct save slot loads.
  • Options menu: Change every setting (volume, graphics, controls, subtitles) and confirm it takes effect immediately. Restart the game to ensure settings are saved.
  • Inventory and character screens: Equip, use, drop, and compare items. Check for tooltips, stat changes, and weight limits.
  • Text and localization: Check for overlapping text, missing characters, and text that extends beyond its box. If you support multiple languages, test each one for string length and special characters.
  • Accessibility: Test with subtitles on/off, colorblind modes, and remappable keys. Ensure UI elements are readable at various resolutions.

Performance and Stability

Performance issues can make a game unplayable, even if the code is correct. Test on a range of hardware, including low-end machines.

  • Frame rate: Monitor FPS in different scenes, especially during heavy action or large open areas. Aim for a stable frame rate on your minimum spec.
  • Loading times: Measure initial load, level loads, and fast travel. Optimize if load times are excessive (over 30 seconds is often a problem).
  • Memory usage: Watch for memory leaks, especially in long sessions. Play for 2-3 hours and monitor memory. If it keeps climbing, you have a leak.
  • Crash testing: Force crashes by alt-tabbing, minimizing, changing resolution, and unplugging a controller. The game should recover gracefully or at least not corrupt saves.
  • Background behavior: Test what happens when the game loses focus (alt-tab) and regains it. Sound should pause/resume correctly.

Audio and Visual Polish

Bugs here may not break the game, but they break immersion and can be jarring.

  • Sound effects: Every action should have appropriate audio feedback. Check for missing sounds, incorrect pitch, or sounds that play at the wrong time.
  • Music: Music should loop seamlessly, change with intensity, and not clash with sound effects. Test with music volume at 0% and 100%.
  • Visuals: Check for missing textures, flickering objects, clipping, and z-fighting. Test at different resolutions and aspect ratios.
  • Cutscenes: Ensure they play correctly, lip-sync is close, and subtitles match the audio. Test skipping cutscenes and returning to gameplay.

Platform-Specific Compliance

Each platform (Steam, Epic, console, mobile) has its own rules and quirks. Ignoring them can get your game rejected or removed.

  • Steam: Test Steam achievements, cloud saves, and overlay. Ensure the game launches correctly from Steam and that the store page links work.
  • Consoles: If you’re on console, test controller vibration, suspend/resume, and system-level features like party chat. Console certification is strict.
  • Mobile: Test on multiple devices and screen sizes. Check for battery drain, touch accuracy, and how the game handles phone calls or notifications.
  • Cross-platform: If you have multiplayer, test cross-play between different platforms. Verify that matchmaking, invites, and voice chat work.

Common Mistakes and How to Avoid Them

Even with a checklist, developers make predictable QA errors. Here’s what to watch out for.

  • Testing only on high-end hardware: Your game may run great on your dev machine but poorly on a typical player’s PC. Test on the lowest spec you support.
  • Ignoring edge cases: Players will do things you never imagined. Test what happens if they skip a tutorial, die repeatedly, or enter a room from the wrong direction.
  • Not testing save/load thoroughly: A save that loads in the wrong location or with missing items is a major bug. Test loading saves from different points in the game.
  • Forgetting to test the final build: The build you submit to the store may differ from your dev build. Always test the exact build you plan to release.

Frequently Asked Questions

How long should I spend on QA?

There’s no set time, but a good rule is to spend at least 10-20% of your total development time on QA and bug fixing. This includes both your own testing and time for external testers.

Should I hire a professional QA tester?

If your budget allows, yes. Professional testers bring experience and a fresh perspective. However, many indie developers rely on friends, family, and beta testers. Just be aware that they may not catch everything a pro would.

What’s the difference between alpha and beta testing?

Alpha testing is done internally by the development team, focusing on functionality and major bugs. Beta testing is done by external players, focusing on balance, polish, and finding bugs in real-world scenarios. Both are valuable.

How do I prioritize which bugs to fix?

Prioritize by severity and frequency. A crash that happens to 1% of players is more critical than a cosmetic glitch that happens to 50%. Fix anything that blocks progression or corrupts saves first.

Should I test on multiple operating systems?

Yes, if you support Windows, Mac, and Linux, test on each. Even if you use an engine that claims cross-platform support, there can be differences in drivers, file paths, and input handling.

What is a regression test?

A regression test is re-testing previously fixed bugs to ensure they haven’t reappeared. After you fix a bug, always test it again, and also test the area around it to make sure your fix didn’t break something else.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.