Issue #7 - Beta and Testing
We see this tag all over the place recently: Beta. Many games pretend they were in some kind of testing phase they call a “beta”. The result of this differs, though. While games like Minecraft and Firefall use the beta greatly to gather feedback from the community on what direction the game should take, some games (mostly ports to a different region) use it merely for server stress tests. Other games are fully finished already, but they’re pushed into a beta to “outsource” the bug hunt to the community.
Then ... What makes a beta?
Well, the model used to be split into a developer-internal alpha phase, a consumer-focused beta and then final release. The alpha phase was used to build the game and try out whether or not the components implemented fit together and actually work.
The beta phase on the other hand was used to get gameplay feedback from consumers. In the long run, the extensive use of paths the developers couldn’t even think of and the difference in thought the various testers present led to discoveries of not-yet-found bugs and issues when it comes to multiple players involved (regarding multiplayer games or modes, of course).
With the Internet on the rise and gamers being more informed about their favourite games, another phenomenon popped up: Marketing betas. Consumers felt “special” when involved in a beta. As such, creating a beta for the sake of attracting consumers became a common practice. Using the beta tag to tell gamers they could join an elite group is simple marketing – and it works.
The model of a closed beta as opposed to an open beta supported this just as well. A closed beta would result in an even more elitist feeling, while an open beta still has the tag – therefore makes people feel more like game veterans if they stick to the game over time. Gamers want to feel special, in any way possible. This also led to a common perception in a gamer’s mind:
“I am playing it before others can!” – not “I am testing this game!”
But then, what happened to the testing?
Testing turned out to be secondary. Games would enter beta phases as fully finished games, close to the release. The main focus was on rooting out major bugs that just weren’t found yet, and stressing the servers. While this may be considered “testing” in regards to the game’s playability and the server capacity, it is just a minor part of the testing involved when releasing a game.
Looking for every small bug, trying to root out typos in descriptions, checking whether it is playable across hardware, giving feedback on game features – This all moved out of the focus of a common gamer. But it’s the common gamer who wants to join betas at any cost, rather than being an honest tester.
The companies lost the focus just as well, though. Why test game features if that’s exactly how we want the game to be? Why look for minor bugs when we had a huge QA internally looking for these bugs on the one path we want the player to take? These conceptions cause the companies to not even ask for the feedback on their beta-introduction or not providing any means of communication.
This doesn’t happen quite too often, though. But these two extreme views from the consumers’ side and the company’s side are becoming much more common and might at some point even make up a large chunk of our industry.
Where do these movements come from?
The answer is simple: Game ports. A fully finished game from Asia can be copied, translated and released in Europe or the US cheaply and easily. Once that’s done, all that needs to be tested are the servers, and possibly some errors in the translation.
Such games pop up every now and then, and they remain rather successful in an era of manga and anime loving youth. The artistic style is appealing and the stories resemble what the other media provide.
The aforementioned marketing betas are just as counter-productive for the old mindset. Gamers get used to the beta phase being a “special” release, and companies get used to a working model to attract players.
Then, when an actual beta shows up, a full testing phase, possibly even mid-development, the average gamer is frustrated. Why isn’t this a full game as he expected? Why are there so many bugs and missing features?
The player either sticks with the game through the entire beta phase, suffering from the testing phase, or he leaves over it simply not fulfilling what he wants it to.
As such, the modern mindset hurts the games that fulfil the old beta standards.