Bug Reporting FAQ

We have compiled some frequently asked questions regarding situations encountered after a bug report has already been successfully submitted.  

Who accepts and rejects bug reports?

• Most of the time, the testing manager (customer) reviews all of the bugs and accepts or rejects as necessary. Other times, the project manager (uTest) will review the list for obvious duplicate bugs or those that require additional information.

I was asked for more information on my bug, how do I document and prove that a bug is real?

• Provide relevant attachments such as screenshots and video captures. Please upload these video captures directly to the uTest Platform. Many more tools and resources are available on the Forums under Useful Testing Tools and Applications.

Why is my bug accepted as Feedback?

• When a reported bug is not considered a bug, the customer may still consider it useful - thereby accepting the bug as Feedback. Keep in mind that this reclassification is typically the exception - not the rule. In other words, if the customer is not looking for feedback (e.g., usability), please do not submit feedback as bug reports. As a tester, bugs that are accepted as feedback will not hurt your uTest rating. Also, you will be paid at a predetermined rate noted in the bug payout table (under the test cycle's Product & Settings tab). Remember, if you report unsolicited feedback on a test cycle, you do so at your own risk. Focus on the scope and instructions and use the Chat Feature to ask questions to the customer and project management team (however, never post a bug to the Real-Time Chat to request if it is valid or not).

What does the bug status 'Info Requested' mean?

• This means that the customer has requested more information from the tester. You will need to review the customer's comments, provide additional information, and click on the "Send Requested Info" button for the bug to be moved back into the "New" status. 
• Important Note: simply replying to the Tester Messenger will not push your bug back into the "New" status. If you do not take action to move your bug back into the "New" status, you risk having your bug rejected when the test cycles closes.

When should I discard a bug?

• Prior to submitting a bug, all testers should carefully ensure that the bug is not a known or previously submitted bug. To verify your bug against known bugs, click on the “Known Bugs” document under Scope & Instructions (if provided). To verify your bug against previously submitted bugs, click on “Bugs and Test Cases” and filter bugs by the specific test cycle you are submitting bugs for.
• However, if you do in fact submit a bug that has already been submitted or perhaps you realize that it is not a bug, you have the ability to discard your own previously submitted bug if and only if the bug has not been reviewed yet. In other words, if the customer or project manager has not initiated a Tester Messenger conversation, or approved/rejected your bug yet, you may remove your bug by clicking on the bug report and then clicking on the Discard button to delete your bug (the Discard button is located on the individual bug report page, immediately above the Tester Messenger). This will remove your bug permanently and avoid potential rejections due to carelessness or oversight.

Is there a limit to the number of bugs I can report?

• If you are new to uTest and have not submitted any bugs yet, you will start out with a limit of five unapproved bugs per test cycle. When one of your bugs gets approved, you will be able to submit one more bug; so on and so forth. If you perform well in your first few projects, this restriction may be lifted. Specifically, if you are a Gold, Silver, Bronze or Proven rated tester, you will not have a bug limit per test cycle. Maintaining a high bug approval percentage and participation level will ensure that you maintain your Gold/Silver/Bronze/Proven status, thereby eliminating the five unapproved bugs limit.
• If you do not have a badge, be especially cautious for your next several test cycles and submit bugs that you are fairly certain will be approved (provide relevant attachments where applicable). Focus on increasing your overall bug approval percentage so that your rating will increase. This will not only benefit you by being able to submit more bugs per test cycle, but also by increasing the number of invitations to private test cycles
• Remember, test cycles may lock well before the stated "End Date" listed in the platform. Therefore, if you're able to participate in a test cycle, please do so as early as possible, submitting in-scope findings sooner rather than later. When a test cycle locks, it may not reactivate again, so do not count on submitting any bugs unless the customer or project manager mentions otherwise in the Real-Time Chat.

• Can I submit a "placeholder" bug report?

No. When you submit a bug report, finalize all contents of your report before clicking on the "submit" button. Although you may return to your bug to make minor edits, you must not make major edits to your report - including bug title, actions performed, expected results, and actual results. The reason this practice is prohibited is because it severely hampers fellow testers’ ability to spot duplicate bug submissions (duplicate bugs are rejected). If you happen to observe other testers creating placeholders, please send an email to testers@utest.com with relevant screenshots of this violation.

• I started to report a bug, but the test cycle became locked. What can I do from here?

If a test cycle becomes locked, you cannot submit any bugs or test cases (even if you are in the middle of submitting a new bug). You can wait for the test cycle to reactivate again or wait for the next one to activate (if applicable). Remember, only bugs and test cases that are submitted through the uTest platform will be considered for approval and payment.

• Why is the "File Bug Report" button disabled?

First, you need to make sure that the test cycle is marked "Active" in order to participate. Next, click the "Accept Test Cycle" button under the Test Cycle Agreement if you are willing and able to perform testing during the specified time. If you performed both of the tasks above, there may still be instances where the "File Bug Report" button is disabled. For example, the customer may only be looking for test case results and has thereby disabled the ability to report any bugs. The opposite case is also true; the customer may only be looking for bugs as opposed to test case results. Also, there are times when bug reports cannot be submitted against an active test cycle, especially after unusual spikes in participation. Please standby and wait for further announcements from the project manager before attempting to submit subsequent bug reports. Finally, there is one more scenario when you may be unable to submit any more bugs and/or test case results: Your tester rating is below the Proven tier. If this is the case, you have a limit of five unapproved bugs per test cycle.

How to file a bug report:

Bug Report template: