Quality Assurance
What is quality assurance? How is it different from a quality consultation?
Unlike the overarching evaluation of a game’s general flaws, quality assurance is an ongoing deep dive into game builds, their recurring issues, stability, and stress testing. This can involve regression testing, test case creation, documentation, and more.
Regression testing:
Regular testing to ensure a game build works as expected
Finding where and how functionality breaks, new and old
Logging issues and clearly delineating bug testing progress
Test cases:
Defining reliable and repeatable steps to thoroughly test game builds, keeping track of common failures
Creating a robust structure for other contractors to work off of
Finding as many issues as possible before they reach end users
Glitch hunting:
Outside-the-box thinking to break games in time to fix them
Extreme attention to detail with an in-depth understanding of the causes behind issues
Repetitive testing with clear steps to reproduce problems that catch acute and hidden issues alike
Stress testing:
Testing with a variety of devices, environments, and conditions
Pushing a game to its limits to conform to platform standards
Soak testing and repeat playthroughs to find memory leaks and progression failures
Documentation:
Setting up bug testing software structure
Identifying testing and pipeline standards for other contractors to follow
Clear progress tracking for team synergy, development timeline reduction, and ease of use
