Test Phase Nomenclature & Player Expectations
Test phases are equally exciting, scary, but also crucially important in bringing the game to the players.
One aspect that sometimes can be a little difficult to pin point is what to name the test phase? Ultimately it comes down to your research question of what you’re looking to learn and find out with this test phase. But depending on the name it will prompt and come with a certain player expectations as well.
What are typical naming for test phases, and what are the subsequent player expectations?
| Technical Test | Alpha | Beta | Stress Test | Early Access | |
|---|---|---|---|---|---|
| Purpose | To test a specific feature of the ecosystem Examples: Account integration and download flow, matchmaking, arena shooter, etc. |
Test feature(s), and help direct the game based on player feedback | To test final stage of the game. Used as a purchase decision for the final product. |
Stress Test Infrastructure Main KPI: High CCU / Traffic |
To be treated as the game launch. |
| Example Research Question | “Does our system remain stable when 500+ players download the game and log in for the first time?” | “What is disliked by the community and can be dropped?” | “What tweaks are needed for a smooth launch?” | “Where does the funnel fail?” | “What features have we not thought about?” |
| Duration | Up to 1 week | 1-2 weeks | 1-2 weeks | 1 weekend | 9-12 months |
| Game Completion | Far from complete. Pre-Alpha state |
Most core features complete | Feature Complete In open beta all that’s missing is Day 1 patch |
Feature Complete | Core gameplay in place and working Additional features missing |
| Player Expectation | - Limited access to parts of the game - Lots of bugs - Not polished at all - Feedback is likely to be implemented |
- Game is missing major parts - Lots of bugs - Not polished at all - Feedback is going to be implemented |
- Game is complete, this is what players get should they buy - Main bugs are fixed with Day 1 patch - Not fully polished - Only major feedback points will be implemented |
- Game is complete, this is what player gets should they buy. - Bugs are present, expected to be fixed with Day 1 patch. - Not fully polished. - Feedback will not be implemented |
- Core game is complete. - Bugs are present, expected to be fixed in upcoming releases - Mostly polished - Feedback will be implemented in regular release cycles. |
| Timing | Far from release | Far from release | Closed Beta: Release is <6 months away Open Beta: Release is <1 month away |
Release is <1 month away | This is practically release |
Naming your test phase accurately can help you manage the player expectation for what state the game is in, as well as provide better information and data for your research question.
Obviously, one can choose to deviate from these. But this will come with a heavy lift of explaining and educating the player on the reasons for the deviation. It’s a setting of expectation and managing them well, which is hard to do outside the established expectation parameters.
If you are looking to plan out your test phase, we have a number of ways how we can help with preparation, risk assessment and mitigation, survey design, and feedback processes. If you’d like to learn more you can reach out to us here!
