Just in case you haven’t already realized it, we value quality extremely highly, and as a result we have included a score so that you can track yours. It is comprised of the following elements:
If your bug reports are approved by the team leader, then you’re clearly providing high-quality bug reports and we want to acknowledge your work.
When your bug reports are rejected by the team leaders for being out of scope or because you have not followed the instructions, it is a sign that your testing has not accurately met the test specification. As a result, these types of rejections will reduce your quality score more than other rejection reasons, so be sure to read the instructions carefully.
Reporting new and original bugs is far more valuable and skilful than reporting the same things again and again. We want to try and give extra credit for finding new bugs.
How to increase your quality score
The following tips will help you improve your quality score and in turn your performance level:
- Report bugs that accord to our rules to increase the chance of them being approved by our team leaders. Since every report we have to reject costs test IO money, you increase your value as a member of our team if you reduce these costs.
- Read the test instruction carefully to ensure you only submit bugs that are in scope. If you are not sure about the scope, ask the team leader via the test chat.
- Don't copy and paste reports from previous tests.
It's not a drama if individual bug reports get rejected. What matters is your performance over a longer period of time and regarding all of your submitted reports during that time frame.