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 discussion thread to ask questions to the customer and project management team (however, never post a bug to the discussion thread to request if it is valid or not).

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 in fact 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.
• Additionally, there may be times in which you run into a test cycle bug limit that is not related to your rating. In these cases, the bug limit is not related to a tester's rating but rather the customer's budget for the project. When this happens, be mindful that the project may become active again, but the standard bug payouts may be altered. Please view the "How much do I get paid" article for more details about payout changes.

How to file a bug report:

Bug Report template: