As you might have noticed, we value quality extremely high, 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 and Reproductions are approved by the Team Leader, then you’re clearly providing high-quality bug reports/Reproductions and we want to acknowledge your work.
When your bug reports/Reproductions 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.
How to increase your quality score
The following tips will help you improve your quality score and in turn your performance level:
Report bugs and submit Reproductions that follow 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.
It's not dramatic if individual bug reports/Reproductions get rejected. What matters is your performance over a longer period of time and compared all of your submitted reports during that time frame.