Quality Assurance Management: 10 Golden Rules

Introduction

When we surveyed over 175 developers about their biggest irritations with their quality assurance management (QA), 43% revealed that their main issue was managing resources and the time allocated to testing. This highlights a concerning reality: many developers, especially freelancers, suffer from a poor understanding and management of quality assurance (QA). In this article, we present a list of ten essential practices to optimize your QA management, to maximize the impact of your game while mitigating resource and time issues.

1. Understand the intricacies of effective QA management and test

The first step to effective QA management is understanding how to sequence tests throughout development. This involves planning key moments for testing so that they integrate naturally into the development cycle, avoiding costly interruptions. A solid plan with contingencies is essential.

Tip: For that, our series of articles on QA planning can offer some tips on this subject.

2. Automate certain tests to save time

Test automation is an essential strategy to save time and resources. It allows for the repetition of tests without manual effort, ensuring broader test coverage and faster problem detection. There are several solutions available, some of which do not require you to alter your game’s code. Each option has its advantages.

Tip: To help you choose automated testing methods, here is an article on test automatization and when/how to approach it.

3. Set up an efficient build delivery pipeline

A well-structured build delivery pipeline allows you to deploy testable versions of your game smoothly and regularly. This facilitates early bug detection and ensures a more consistent workflow.

Tip: To maximize the returns on your efforts, look into best practices for labeling game versions, and choose a reliable delivery tool.

4. Build “rock solid” documentation: GDD/TDD, etc.

Solid documentation is the backbone of a good QA process. Documents like the Game Design Document (GDD) and the Technical Design Document (TDD) should be detailed and up-to-date, providing a clear framework for development and testing.

5. Design a concise and complete backlog

A well-designed and exhaustive backlog is crucial for effective QA management. It should include all necessary tasks, properly prioritize them, and ensure regular follow-up.

Tip: Establish a detailed backlog and update it frequently to reflect changes and new priorities. Game Developer has written a good article on this subject.

6. Clearly define everyone’s roles for better cross-team collaboration

Clearly defining roles and responsibilities within the development and QA teams facilitates collaboration and minimizes misunderstandings. It also maximizes testing efficiency. Prioritize your teammates’ aptitudes and natural interests to assign them to certain areas of test. Ask them what they’re motivated by and want to tackle. You’d be surprised in more ways than one!

7. Practice open, transparent, and regular communication

Proactive and transparent communication between developers and the QA team is essential to quickly identify and resolve issues. This helps keep everyone on the same page and prevents misunderstandings. Beyond this, promote open communication and ownership among all contributors to your project.

8. Draft a good bug report

A well-structured bug report template helps document issues clearly and concisely, making them easier to resolve. A good bug report should include precise details about the problem, how to reproduce it, and the affected environments. Use fields such as:

Summary
Actual result
Expected result
Steps to reproduce
Notes

Make sure to include attachments and logs whenever possible to help your partners better understand the issue.

Tip: Ensure you have a concise bug report template with defined sections and clear references.

9. Accurately plan time for localization testing

Localization testing is often overlooked but essential for games intended for an international audience. It is crucial to allocate sufficient time for these tests to ensure your game is well adapted to different markets. To do this, take the number of words in your script, including all menus and options. Generally, you can take this number, divide it by 1000 (typical velocity for localization checks), and add the number of hours of your playthrough.

Tip: For example, if a game has 20,000 words and a playthrough of 20 hours:

Localization time: 20,000/1000 + 20 = 40 hours (script/velocity) + playthrough length

10. Regularly conduct UX tests to detect what your users want to see

User experience (UX) tests should be conducted regularly to understand what your players expect from your game. Focus groups and other UX testing methods can provide valuable insights to improve the game.

Tip: Regularly organize focus groups and analyze user feedback to adjust your development. For this, we have written an article on best practices for organizing an internal playtest.

Conclusion

In conclusion, quality assurance is a crucial but often poorly managed step in game development, especially for developers facing time and resource constraints. By identifying the ten main pitfalls that waste the most time, we have highlighted key areas where improvements can be made. By adopting the proposed remedies, such as better resource management, test automation, and solid documentation, developers can optimize their QA process and avoid the stress of crunch time.

Our goal is to provide developers with the tools and knowledge necessary to better manage this essential aspect of their project. By applying these best practices, you will be able to deliver a superior quality game, while respecting deadlines and minimizing frustrations related to inefficient QA management. We hope this article has provided valuable insights that you can successfully integrate into your future development projects.