a) Verify the tickets added by the client, as they’re one of the most important pieces of the puzzle.
- See if any recent tickets are duplicates.
- Since a ticket is as useful as its description, you must check if the tickets have clear steps written down; if not, take care of it.
b) Tickets should contain other useful information in the shape of fields, labels, and components specific to each project.
*They offer secondary (but no less important) info about the content of every ticket.
c) Difficulties caused by bugs can encumber users or even block their navigation on a web app. However, not all of them are equally crucial for the teams working on the project.
- Make sure every bug is evaluated correctly and its priority is set accordingly.
- When in doubt, ask the product owner about it.
These are just a few steps we recommend every QA follow at the beginning of every workday to maximize their efficiency.