Regression pass
Also called: Regression testing, Regression run
A regression pass retests features that already worked after a code change, to catch bugs the new patch broke in old parts of the game.
A regression pass is a planned retest of existing features after a change to the build. A fix in the inventory code can break crafting. A new localization file can push text off a button. The pass exists to catch these side effects before players do.
On Steam, the regression pass usually sits between the last fix and the moment a build goes live on the default branch. For a patch, testers play through the changed systems, the save and load path, achievements and the main menu settings. Saves made on the previous public build are part of the check, because players will load them.
QA keeps a regression checklist that grows with every release and runs it on the exact build that will ship. Anything that fails gets a report with repro steps and the build ID of the last version where it worked. The patch day checklist on this site is one ready-made starting point.
Updated · Written by JJ, founder of Jumbo Jelly.
Where to read more
Related terms
- Day-one patch
A day-one patch is an update released on or right after launch day to fix bugs found after the release build was locked or once players arrived.
- Smoke test
A smoke test is a short check that a new build starts, loads and runs its main loop, done before deeper testing so nobody wastes hours on a broken build.
- Build ID
A Steam build ID is the global number Steam assigns to each uploaded build of a game, used to tell builds apart and to set one live on a branch.
- Repro steps
Repro steps are the numbered actions that make a bug happen again on demand, written so a developer can trigger it without asking the tester anything.