This document is meant as a guide to help new/intermediate testers on our platform to better understand and organize the way they submit issues on any Tester Work cycle.
Firstly, please note that this guide is a general one and any cycle has particularities and individual requirements that might affect the Severity/Steps/Needed Attachments/etc. of an issue. That is why reading the Specifications Document present in any test request is not only vital but mandatory.
That being said, if you follow this guide you should be able to upgrade the way you submit bugs and increase your ranking by having fewer mistakes that need correcting by moderators, and fewer invalid issues altogether.
Let’s begin:
- Main elements of any bug and how you should describe them
- Severity: Some bugs are more valuable than others
- Steps: Where a bug lives and how it can be found
- Correct attachments: An often overlooked aspect of bug reporting
- Outcomes: The fate of your issue
- Poor quality reports: Why grammar and proper communication matters
- Not in Scope: Usability issues and more
- Moderators are human too: Sometimes a bug can slip through the cracks
Comments
0 comments
Article is closed for comments.