Open Category List

Tips for Managing Bug Approvals

2 minutesread

Use Your Test Team Leader (TTL)

HOW THEY CAN HELP YOU:

  • The goal of the team test leader is to speed up your triage process and manage the testing group.

Recommendations

  • TTLs are asked to review and replicate every issue within 24 hours of filing when volume allows.
  • For each issue you should see a recommendation: Could they reproduce, Was it a duplicate, Is it in Scope, and do they recommend Approval and what value or Rejection.
  • NOTE: If you are in line with the TTL’s judgement and time is pressing you can do a batch approval by approving all tickets at the recommend value.

Report Quality

  • The TTL is asked to review that every report has all the information you requested and has provided clear steps and followed our reporting standards. They may also leave a comment under the recommendation section to explain further.

Requests

  • The TTL is your immediate source to help redirect testers or modify instructions. Feel free to reach out to them if something needs to change during a cycle.

 

Triaging Early In Cycle

WHY IT’S IMPORTANT TO YOU:

  • When you start approving issues testers tune in immediately to learn what is valuable to the client and what is being approved and rejected. Doing this while the cycle is active early is a means of keeping them on focus.

 

When to Use Works as Designed

WHY IT’S IMPORTANT TO A TESTER:

  • When you reject for this reason their tester ratings are not affected, so anything that they could not have known should be rejected as WAD.

WHY IT’S IMPORTANT TO YOU:

  • The Works as Designed button (as well as Approving as “Won’t Fix) is designed to encourage testers to submit issues when they are unsure about them, so potential concerns aren’t missed for fear of rejection.

 

Bug Severity VS. Bug Value

When to Over Value a Bug Report:

Limited Scope:

  • There are times when the issue itself may not be that severe to the site, but because of a limited scope, or a mature product, the tester has found something right on target to the task given in scope. In those situations it may be appropriate to value the bug based on being on scope rather than the priority level it will be assigned.

High Effort/High Quality Testing:

  • Occasionally you will see some high quality testing that required a lot of effort but the value of the issue is not that big a concern. Feel free to reward good testing/reporting as well as high priority issues. This keeps them going for more.

 

Too Many Somewhat Valuables

WHY IT’S IMPORTANT TO A TESTER:

  • Testers are paid according to your value of the bug and the scale is significantly weighted to provide them incentives for looking for high value issues. If too many of their bugs are being valued at the lowest level, they will stop testing to avoid diluting their rating.

WHY IT’S IMPORTANT TO YOU:

  • Assigning the right value to a bug is the ultimate aligning of expectations for our testers. For your sake, approving as very or exceptionally valuable is telling the testing pool “this is what I want to see the more of” – when appropriate of course.

Too Many Very Valuables

WHY IT’S IMPORTANT TO YOU:

  • Conversely to the above, if too many tickets are overvalued you will see testers throw a lot more against the wall, and you may see them “over reporting” the same issue in different locations in order to garner another high payout.
0
0
29
2 minutesread

Related Knowledge Base Posts