Regression Testing

Quantitative:

Quantitative data answers what is happening using numbers
(e.g., error counts, completion rates, time on task, crash frequency)

Best Stage: Ongoing Development → Post-Update

Primary Goal: Ensuring new changes don’t break existing features, systems, or fixes

Effort: Moderate

Overview

Regression testing refers to the process of retesting parts of the game that were previously working to ensure the new updates, bug fixes, or features haven’t accidentally broken the build.

How it's done:

Manual Regression Testing: QA testers replay key parts of the game that could be affected.
Automated Regression Testing: In some studios, tools/scripts automatically test common actions like loading levels, interacting with menus, or moving the character.
Checklists: Many studios keep a regression checklist of past bugs and features to quickly verify after every build.

Example of Regression Testing:

You fixed a bug where players couldn’t pick up health potions in Level 3.

During regression testing, you would:

Retest Level 3 to confirm the health potion bug is fixed.
Also check Levels 1, 2, and 4 to make sure potion pickup still works elsewhere.
Verify that fixing the bug didn’t break inventory, combat, or save/load functions.

This ensures the fix didn’t cause new problems in features that were already working.

Resources:

TestDevLab. (n.d.). Best practices of regression testing: A comprehensive handbook. TestDevLab. https://www.testdevlab.com/blog/best-practices-of-regression-testing-a-comprehensive-handbook

IXIE Gaming. (n.d.). Ultimate guide for regression testing in video games. IXIE Gaming. https://www.ixiegaming.com/blog/ultimate-guide-for-regression-testing-in-video-games/

QA TestLab. (2022, August 30). Game regression testing. QA TestLab Blog. https://blog.qatestlab.com/2022/08/30/game_regression_testing/

Starloop Studios. (n.d.). Game testing 101: Tips and strategies. Starloop Studios. https://starloopstudios.com/game-testing-101-tips-and-strategies/