How to Verify a Bug: A Comprehensive Guide to Our Workflow
Make sure the bug ticket is on the BUG board and needs verification (Bug tickets on the SPRNT board need to be “tested” not “verified”)
Please note that this guide has been posted with the purpose of training our QA team.
Read over the ticket and make sure there is enough information to proceed
Assign the ticket to yourself & update the status to “In Progress”
Try to replicate the ticket under the same circumstances outlined in the ticket. If the specific circumstances aren’t outlined try a few options, but you can also reach out to the ticket requester or the team if you have questions
If you can replicate the ticket:
Try to narrow down the cases when it would be able to replicate. We want to provide the dev’s with as much information as we can that will help them track down where the bug is coming from in the code.
Figuring out cases to test next will come intuitively with more experience, but brainstorm different cases related to variable pieces in the bug.
What about different Claim Statuses?
Different service dates?
What if the class doesn’t have Benefit X enabled?
Does the member have coverage history records?
If you can’t replicate the ticket:
Because we deal with a lot of edge cases how we deal with tickets that don’t verify isn’t pretty flexible. Best first action is to ask someone else. Probably try one or two more things working together with someone.
If none of us can reproduce it, and we’ve run out of reasonable options then we’ll decide what to do together based on the reasonability and severity.
If gut instinct feels like it’s a real bug, then we’ll switch it to “Needs More Information” and keep an eye out for more examples
If it’s not a huge impact bug, and we suspect its bad-data related then switch it to “Closed” and keep an eye out for more examples
Whatever happens, before you change the status of a ticket to Verified, Closed or Needs More Information make sure to leave a comment (or update the description) with details about what steps you’ve taken to review the ticket
More help articles:
