Book Image

Modern Game Testing

By : Nikolina Finska
Book Image

Modern Game Testing

By: Nikolina Finska

Overview of this book

Few things are more annoying for gamers than encountering a buggy new game. This often leads to negative reviews, and in turn, you’ll find that demand for your games declines. The solution lies in better quality assurance (QA) – and Modern Game Testing will show you how to achieve just that. Whether you’re a new tester, developer or producer, the QA testing techniques shown in this book, using modern methodologies and the latest technology, will have you releasing quality games that are on time and, most importantly, on budget. The book begins by introducing you to QA and the various types of tests that are performed on games. You’ll then explore test cases and bug reporting, building tests for different platforms (even consoles and PCs), and LiveOps and test management. As you advance, you’ll build a QA team from scratch and work with remote QA testers. The chapters help you take a more traditional approach to learning lessons, enabling you to examine the modern agile approach and various testing strategies that you can then adopt. All angles are covered with oodles of examples, so you’ll have everything you need to implement QA strategies in your organization. By the end of this book, you’ll have a clear understanding of the modern methodologies of QA testing for games, and be able to build efficient, reliable, and long-lasting QA teams.
Table of Contents (19 chapters)
1
Part 1: Game Testing Foundation
7
Part 2: Test Strategy and Execution
13
Part 3: Test Management and Beyond

Severity versus priority

Severity and priority are sometimes used interchangeably, and that causes even more confusion in understanding what they really are. In fact, severity and priority are very different, and they should be looked at separately when writing bug reports. Priority indicates how urgent it is to fix or address something. Severity indicates how big an impact this bug has on the end user. When QA reports bugs, they act as a representative of the player, and they should have a good grasp of the severity of the bug. But a decision about priority is rarely in the hands of QA. While QA can certainly recommend how quickly something should be fixed, it’s up to the producer to decide the final priority of the bug. The producer will have the full picture of the roadmap, stakeholders’ interests, and team capacity and will make decisions based on those factors.

In the following table, we can see what the main distinctions between priority and severity are:

...