Bug Review Process

The bug approval process is as follows (similar with all other reports - including test cases, surveys, etc.):

1. Tester submits a bug in a test cycle (after accepting the Test Cycle Agreement on an Active test cycle)
2. The bug moves into the "New" status (on certain test cycles with Test Team Leads, your bug may be pushed to another state called "Pending Approval." This simply means that your bug has a recommendation by a Test Team Lead - the recommendation is only visible to the customer)
3. Depending on the customer's preference, the bug may be reviewed while the test cycle is still active or after it becomes locked. (most bugs are reviewed within one week of the test cycle becoming locked)
4. Once the customer reviews a bug, the bug may be moved into the following statuses:

• Approved: Bug is approved and the payment is credited into the tester's pending payments
• Info Requested: Customer has requested more information from tester. The tester needs 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 "Pending Approval" status. If you do not take action to move your bug back into the "Pending Approval" status, you risk having your bug rejected when the test cycles closes.
• Rejected: Bug is rejected by the customer

5. When a bug is rejected, the tester may choose to dispute the rejection. However, each has a limited number of disputes per month, so please choose which rejected bugs to disputes wisely. Dispute statuses include:

• Disputed: The tester decides to dispute a rejected bug and has one chance to provide further evidence of the bug
• Under Review: The customer has rejected a disputed bug and will not review any further evidence. However, the project manager may review, depending on the test cycle schedule and end date. If a report remains in the "Under Review" status when the test cycle closes, the report will be eventually marked as "Rejected" (you will also receive an email with Reason listed as "Other" and Explanation listed as "Test cycle closed")

FAQ: How long do I need to wait until my bug is reviewed? (similar with all other reports - including test cases, surveys, etc.)

• The review timeframe will vary. There are some customers who consistently review reported bugs as they trickle in. For example, the test cycle may still be active, but the customer is already approving or rejecting bugs as they are being reported. On the other hand, there are also customers who wait until the test cycle is complete before reviewing the reported bugs. As a general rule of thumb, please allow 35 days after the test cycle clocks before sending a request about why your report has not been reviewed yet. You may request this information by emailing testers@utest.com.