Bug Types: How to Recognize and Categorize Them

Before we begin, please remember that each test cycle has its own specific rules and requirements. These may influence severity, steps, required attachments, and other aspects of issue reporting. For this reason, carefully reading the Specifications Document in every test request is mandatory.

By following the guidelines outlined in the following articles, you can significantly improve the quality of your bug reports, reduce the number of moderator corrections, and minimize invalid submissions. 

In these articles you will get familiar with:

• The Basics: The Tracker

• Key Elements of a Bug Report and How to Describe Them

• Severity: Why Some Bugs Are More Valuable Than Others

• Steps to Reproduce: How to Clearly Show Where and How the Bug Occurs

• Correct Attachments: A Commonly Overlooked Requirement

• Outcomes: What Happens to Your Issue After Submission

• Poor Quality Reports: Why Clear Vocabulary and Communication Matter

• Poor Quality Reports: Why Grammar Matters

• Not in Scope: Ensuring Your Bug Is Valid

• Moderators Are Human Too: Why Mistakes Sometimes Happen