Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Modern Game Testing

You're reading from   Modern Game Testing Learn how to test games like a pro, optimize testing effort, and skyrocket your QA career

Arrow left icon
Product type Paperback
Published in Jul 2023
Publisher Packt
ISBN-13 9781803244402
Length 232 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Kalle Kaivola Kalle Kaivola
Author Profile Icon Kalle Kaivola
Kalle Kaivola
Nikolina Finska Nikolina Finska
Author Profile Icon Nikolina Finska
Nikolina Finska
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Part 1: Game Testing Foundation
2. Chapter 1: Setting the Stage – Introduction to QA for Modern Games FREE CHAPTER 3. Chapter 2: All Engines Go – The Basics of Game QA 4. Chapter 3: A Deeper Look – Types of Testing in Games 5. Chapter 4: Deeper Look – Testing on Various Gaming Platforms – Mobile, PC, and Console 6. Chapter 5: It Must Be Hardware: Testing Hardware in Modern Game QA 7. Part 2: Test Strategy and Execution
8. Chapter 6: Friend or Foe – Test Cases 9. Chapter 7: It Works on My Machine: Bug Flow 10. Chapter 8: I Thought I Fixed That: How to Write Efficient Bug Reports 11. Chapter 9: It Works, but It Hasn’t Been Tested: Testing Approach 12. Chapter 10: Eat, Sleep, Test, Repeat: Test Methodology 13. Part 3: Test Management and Beyond
14. Chapter 11: Are You on the Right Version? Live Ops and QA 15. Chapter 12: Beyond Testing – Introduction to Test Management 16. Chapter 13: There Are No BUGS Without U – QA and the Game Team 17. Index 18. Other Books You May Enjoy

Bug reporting best practices

We have learned now about what should be included in a good bug report and how it should be structured. While every gaming studio might have different production practices, there are certain bug-reporting practices that can be implemented in any game team. Let’s look into them more closely.

Reliability

The bug report should be factual and present the real issue as it happened, without embellishment or additions. While it’s incredibly useful to add additional information and supporting documentation and files, such as screenshots, QA should restrain from presenting opinions as facts. Bug reports have a commentary field where QA can express their opinion on the bug, but as such: an opinion. Presenting it as a fact might cause a lack of trust in QA, throw the coder on the wrong track, and, in return, can affect bug-fixing rates and timelines. When we report bugs, we want to make sure that developers and other stakeholders reading bugs can...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime