Most broken game builds that reach players aren't broken in subtle ways. They crash on launch, lose a save, or freeze when the controller gets unplugged. These are things a short, repeatable smoke test would have caught.

Here's the checklist we keep pinned for builds that go to testers, publishers, or a storefront. It takes about 30 minutes, needs no special tools, and works for Unity, Unreal, Godot, or a custom engine.

1. Install and launch from scratch (5 min)

  • Uninstall the previous build and delete its local save and config folders, then install the new one fresh.
  • Launch on the lowest-spec target you support, not your dev machine.
  • Check the first-run flow: EULA or consent screens, language selection, and the default graphics settings.
  • Make sure the build number on the title screen matches the one you think you're shipping.

2. Core loop pass (10 min)

  • Start a new game and play through the first real gameplay beat: one level, one match, or one session.
  • Pause, resume, and quit to the menu in the middle of play.
  • Trigger one win and one fail state.
  • Open every top-level menu once. A dead button in a menu nobody tested is a classic last-minute bug.

3. Save and progression (5 min)

  • Save, quit fully, relaunch, and load. Confirm that position, inventory, and settings all survive.
  • Kill the process mid-save if your platform allows it, then relaunch and confirm the game recovers without corrupting the save.
  • If you have cloud saves, test with the network off and then on.

4. Input and device edge cases (5 min)

  • Unplug the controller mid-game. The game should pause or show a prompt, not crash or keep running.
  • Switch between keyboard/mouse and gamepad and check that the on-screen prompts update.
  • Alt-tab or background the app (mobile: lock the screen, take a call) and return.
  • Change resolution or rotate the device if you support it.

5. Platform basics (5 min)

  • Achievements/trophies: unlock one and confirm it registers.
  • Suspend/resume on console or handheld targets.
  • Check that no debug overlays, test menus, or placeholder text are left in.
  • Skim the log for new errors or warnings compared to the last build.

Make it stick

  • Keep the checklist in the repo next to the build script, so it's versioned alongside the game.
  • Rotate who runs it. Fresh eyes catch the things the feature owner has learned to ignore.
  • Log failures as tickets right away, with build number, device, and repro steps. "It crashed once" with no context costs a day later.
  • Block the release on any step-1 or step-3 failure. Launch crashes and save loss are the bugs players never forgive.

A smoke test isn't a replacement for full regression or certification testing. It's the cheap gate that stops obviously broken builds from wasting everyone else's time.

I work at Juego Studios, where we build and test games across mobile, PC, and console. If you want to see how a dedicated team structures deeper coverage beyond a smoke pass, here's an overview of our game QA and testing services. What's on your team's pre-release checklist that isn't on this one?