Process

The biggest part of testing is the test cycles – test cycles are mini-projects with a defined area (scope) and a short briefing. The first invitation is likely to arrive in just a few hours after your registration.

When your profile and device(s) match a new test cycle criteria, you receive an invitation by email. You can also find all your pending invitations on your dashboard, listed under “Interesting tests for you”.

If you accept or reject an invitation is up to you. You can join as many test cycles as you want at once, however, consider how much time you will need to test and if you realize you do not have time to test in one test please remove yourself from the test.

If you don’t wish to participate in a test you can reject the invitation. Rejecting and accepting invitations will earn you ranking points (read more about the ranking here.)

As soon as an accepted test cycle starts you can access the test and submit bugs you find.

After joining a test, you can see the test interface on your dashboard.

Screen Shot 2017-03-28 at 12.37.22.png

The test starts after the successful installation of the app / accessing the environment.

You will need to read through all the instructions and information in the product sections. Once you have clicked the show instructions button for an app section, you will then be able to report the bugs that are in scope for that test using the different buttons displayed.

On every test cycle, there is a team leader who can help you if needed, but their main focus is to check the bugs submitted.

The team leader will ask for further information if needed and accepts or rejects your bugs. Bugs accepted by the team leader will be handed over to the customer. Customers can also check the bugs and might reject them. But normally just one out of five bugs is rejected