Any good QA engineer is a well-organized person who has everything established clearly in order to be as work-efficient as possible. From our experience, some things have proven to be essential at the beginning of every workday in order to give the best results possible.

Hence, we have compiled a quick ToDo list which every QA engineer as yourself should go through when work begins.

1. Read your emails and act on them

a) First of all, if you are cc’d in one of the emails you have received, make sure you don’t forget to act on them. Begin by placing tickets in the “Ready for QA” state so the QA team will know what they have to do and not neglect any of the issues at hand.

b) Following this, you need to check if any ticket needs to be reopened for someone to look over it a second time and, of course, don’t forget about the tickets that must be closed once their issues have been tested and found to be resolved.

2. Check the tickets your colleagues have added

Like yourself, your teammates are busy creatures that work tirelessly, day or night. In the past 24 hours, they might have added new tickets on the project you are working on. So, you need to keep yourself up to speed by checking these, meticulously.

There are some priorities when it comes to checking tickets.

a) Primarily, you need to verify the tickets added by the client, as he (or she) is one of the most important pieces in all this puzzle. See if any recent tickets are duplicates of existing ones, especially. Given that any ticket is as useful as its description is, you must check if the tickets have concise steps written down; if not, please take care to improve the description.

b) Furthermore, tickets should contain other useful information in the shape of fields, labels, and components specific to each project. These 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, but not all of them are equally crucial for the teams working on the project. Thus, you must make sure that every bug is correctly evaluated and its priority is set accordingly. When in doubt, you could ask the product owner about it as well, if the ticket has a high priority and the steps leading to the bug are adequately written in the description.

These are just a few of the essential steps we recommend every QA engineer to follow at the beginning of their workday in order to maximize their efficiency.