1.1. Let’s start with the basics: the Tracker

In the Tester Spec document and/or the Test Case invitation email you will have a Tracker link that will lead you to the project you will have to submit issues in.

After you find a bug you should always check if the issue has not already been reported in the Tracker by another tester in the current test cycle or in the “Known Issues” list on another version of the app. The bug checker feature can help you search using keywords that match your issue making it much easier to see if your issue has already been reported.

Being careful is therefore very important, as reporting a duplicate will invalidate your issue and you will not receive payment for it. Furthermore, your rank will also suffer for any invalid issue, that’s why it is always recommended to check thoroughly before submitting any bug report. But if you did check and your report is indeed valid and not a duplicate then the next step is to report the issue.

Clicking/tapping on the ‘Report an Issue’ button will lead you to the report page where you will have several fields to complete with accurate information about your bug.

Please note that these fields can vary from cycle to cycle. Some projects require different types of information, but most of the fields will be the same so it’s a good idea to make a mental note of them. Additionally, please note, that the majority of these fields will have to be manually completed by you with your own words - describing the issue or providing the required information. Some fields, however, will be in the form of a drop-down menu from which you will have to select one of the choices. 

Some fields will be marked as mandatory - those you will have to complete to be able to submit a bug report, others, however, are optional because they only apply to certain scenarios or devices. Please do not skip these last optional fields just because you are not forced to complete them, instead review what they require and whether you can provide additional information. You should skip them only if they do not apply to your scenario/device in any way.