Experts from Braze, a mobile engagement automation company, define QA as a ‘key brand differentiator’. Quality improvements influence user experience and engagement, which are the key factors of game popularity.
Appboy professionals release studies about app users retention stating that less than 25% of the first-day users got usually engaged and decided to play the game further. So, they conclude everybody involved in the game development process contributes to user happiness, but QA is still the stage, which can not be omitted. Moreover, they say only 29% of tech companies perform exploratory testing (testers check the product while it’s being developed, not after full completion).
Both developer-based testing and QA are able to deal with commercial release bottle-necks, downtime on production, and decrease the number of significant customer defects. If anybody still doubts QA really provides more people’s love to your titles, here are some examples of the failed games, where not enough testing were performed:
A lot of features are critical for a fun product: music, sounds, dialogues. If you don’t want your game to lose real fun, user engagement, and glory, QA must become one of the mandatory stages in your product software development lifecycle. And you are welcome to read this article to learn more about quality assurance in game design, its place in the software development lifecycle and get more insights about QA types, how to test different games as well as advice on how to find game bugs.
Idea or a concept is a real start for any product. And to make it implemented, a range of stages should be followed. Cliff Bleszinski, a designer for Epic Games known for his Gears of Wars series, says about the game development lifecycle: ‘Nobody in-game industries can predict what their activities are, they just have a gut assumption’. But in spite of this humorous saying, let’s specify what game testing is and which place it takes in the entire game development process.
Game testing is a stage in software development applied for quality management and finding bugs. Testing is demanded during the development cycle to be ready at least for the Alpha launch which is an early version with minimum testing done and with high potential to be unstable.
While testing, the QA engineers must find the answers to the following questions:
Answering these questions is vital because the game has all chances to fail if we do not know whether its mechanic works well if rules and levels are engaging enough to prompt the users to play again and again, what features need to be polished more before Alpha and Beta release. That is why QA is a part and parcel of the game development lifecycle alongside with:
Game development process takes a lot of time and demands a number of iterations, much testing, and launching Alpha and Beta versions, which leads finally to the engaging playable game. Every stage involves testing: exploratory one throughout the whole development process; clean room procedure to assure code reliability; users’ post-production reports as a kind of testing as well. Once testing is so important, we propose to dive deeper into stages, techniques, processes, and approaches to be aware of what is game testing inside.
Marissa Mayer, the Yahoo CEO, noticed in her Twitter: ‘Geeks love tech issues so much, that all the details are of crucial importance’. This quote is relevant to our topic as well. Assuring game quality we exclude irritating bugs and errors spoiling nice game concepts. So, what stages should be followed to create the perfect product?
We propose to follow every stage to learn about objectives, responsible specialists, and the sense of the procedure.
Stage: closed Alpha testing takes place on the preliminary level
Objective: identify bugs, which were not obvious in the earlier development stages
Who performs: a group of users reflecting the real user environment and playing as if it happens in real life after the game release.
Stage: closed Beta. It’s quite similar to closed Alpha but more extensive
Objective: figure out the potential obstacles to the natural smooth playing flow
Who performs: volunteers from the users, not development team members
Stage: open Beta is a stage, during which all users are welcome to play the game and report any poor functionalities
Objective: improve user experience and define any broken code in a production environment
Who performs: every user willing to play
Stage: Fun factor, balance, learnability, or reliability tests
Objective: make live user test process successful
Who performs: real players or focus groups
All the stages involve game testing processes delivered both by QA engineers and real players. We propose to follow every stage for a better understanding of the whole procedure.
Game testing processes align with a basic typical SDLC (software development lifecycle): the game is tested on such aspects as endurance, performance, engaging user experience. In a plane way we can imagine game testing as that consisting of the following processes:
Once we’ve answered the questions ‘What do we do?’, ‘Which tiny processes and operations are included in the activity’, it’s reasonable to answer ‘How do we perform it?’ Let’s consider what the basic game testing techniques are known.
Before commercial product release engineers work on finding bugs and errors. Quality control can be as following:
QA is applied practically on every stage of SDLC being composed with a number of processes and performed in a variety of manners. It could be done either manually or in an automated way. What’s better?
Sometimes the game is tested manually, sometimes the tech team writes special scripts to automate quality control. Both methods have pros and cons. We propose the chart below for better awareness of the differences considering a variety of the parameters.
Manual testing is convenient because it provides:
At the same time automated QA:
For getting the best of human creativity and automation precise efficiency sometimes there’s a need to combine. Exacol, a database developer, counts manual testing as 100 000 times slower than an automated one. They think it makes sense to automate repetitive tasks anywhere in development, but especially in testing. So, consider the pros and cons of both methods, and estimate which proportion of each testing you need on your project just like we do for our clients at Innovecs.
If you want to be aware of time limits, it’s worth imagining that while testing every character must face every other character in every possible game situation on every possible level. It sounds quite time-consuming. It’s a lot of repetitions, which are not only about playing games but about repeating the same game fragment trying to break it. Time should be spent for finding code irregularities, art glitches definition, level bugs outline, and logic game errors excluding.
To be aware of deadlines, testing plans are helpful with detailed objectives, resources, and processes. Of course, it’s possible to evaluate the timeframe for testing considering experience with the same games, your knowledge about testing processes, and awareness of how much time manual or automated testing requires. And we guess the more facts you know about QA, the easier it is for you to imagine the process and plan to outsource game testing. Hence, here are more smart details about bug types, dealing with which is helpful in improving user experience.
The fact that such a giant of the game industry as Sony announced a global Bug Bounty Program proves to us that it’s worth paying a lot of attention to testing if you want to get a profitable product. So, companies seeking opportunities to provide an engaging experience for their users’ community will test the game more and more times to ensure perfect quality. Let’s follow some glimpses concerning which usual bugs are:
Considering all these issues assists in avoiding bothering, annoying and game-breaking experiences. The testing focus should be placed on all of them so as not to miss the tiniest feature able to stress the player and influence on your ROI in the future.
To sum up, in this article we have outlined and described the following:
For your success in launching a bug-free solution, Innovecs provides smart QA engineers who can protect your game from failure risks, execute a variety of test cases to deal with the bottlenecks as well as prevent financial losses due to poor game code. We are a really trustworthy partner with QA expertise applying the latest and greatest new tech solutions.
In the end, we’d like to quote Andrew Moore, the Head of Google Cloud AI, who notes smartly on his Twitter that he’s extremely glad to live in the world, where it’s routine to perform multiple complicated processes ‘in a jiff’. And we could but agree that new technologies (in testing as well) contribute greatly to make outstanding titles efficiently.
The HBS Digital Initiative at Harvard Business School names Unity “a unicorn” enabling video game development and VR/AR economy to grow throughout the previous years. Forbes has talked to Jessica Lindl, Unity’s VP for Social Impact, to catch more information on how the Unity platform brings innovations to boost the creativity of game makers and […]
The mobile game industry is growing substantially. According to the Business of Apps resource, this industry showed a $77.2 billion turnover last year. And they report a 12% online players increase in 2020 in comparison with 2019 due to pandemic situations in the world. Game brands are striving to attract more players to lead the […]
Today many gaming companies dispute the expediency of using game design documents (GDDs). In this article, we want to shed some light on this matter and find out the GDD’s pros and cons. Looking at the future trends in gaming from a user perspective, we see a customer with ever-growing demands to be satisfied and […]