This score is a reflection of how reliable you are when it comes to your testing with us and is comprised of a number of elements.


Determining factors

Contribution rate

In simple terms, we want to display how much you contribute to a test, in terms of bug reports and reproductions per test. So even if you don’t test that often but contribute a lot when you do, this will reflect how valuable your work is. Only team leader approved bug reports and accepted reproductions are considered for this score.

Request rate

Sometimes we need to contact you for more information related to your bug reports and we rely on you to respond in a timely manner. This element of the score simply considers how often you manage to reply to customer and team leader requests within the time limit.

Activity

We love an active tester, but we realize that modern lives are busy and we pride ourselves on providing you with flexible work. As a result, we decided to review your activity over the entire 90-day window in terms of tests accepted, then taking an average to give a fair representation of your testing. So if you have a busy week or you take a well-earned holiday, it will still only have a small impact on your activity rate.


How to improve your reliability score

The following tips will help you improve your reliability score and in turn your performance level:

  • Participate in each test that you accept. If you cannot find any bugs, or if the ones you found have already been submitted by other testers or are on the Known Bugs list, submit reproductions.
  • As soon as you know that you cannot participate in a test, exit it. The earlier you do leave the test, the earlier another tester can take your spot.
  • Respond to every information request sent by a team leader or customer.

It's not a drama if you forget to exit a particular test or could not find time to respond to a particular information request. What matters is your how you behave over a longer period of time and across all tests during that time frame.


Related articles:

Did this answer your question?