In Software Testing it can be very easy to get by doing very little, but on the flip side, it can sometimes feel excruciatingly difficult to stand out.
Here are the tips that I have gathered throughout my career so far that may help you gain recognition amongst your peers and propel your career. As with everything I write, these are not answers swiped from Google but simply my experiences and observations. I consider things I have also read and implemented
Ask Questions…
Then ask questions about the answers that you’re given, then again, and so on. This might be easier to preach than to implement. There are times when you have a genuine question but there will be no doubt, countless times when you don’t have a question or do not have a full understanding of the scenario you’re in. I would still start with a more simplistic question.
Something even as high level as ‘How do we test this?’ or ‘Do we have any acceptance criteria for this?’ This can open the discussion for wider questions. Developers don’t always consider how a change of code can be tested. Simply raising the question can get them to think, and lead to more discussion.
Part of our role as a tester is to help facilitate collaboration and this is one of the best ways to stand out as someone who is attempting to do more than just get by. One of my most powerful tools to make people aware that I am even there is to ask questions I already know the answer to.
Pushback
The attitude towards the testing profession can sometimes be that ‘anyone can test’. While there may be areas of testing that anyone can do, that does not mean for a second these things do not take time. Always giving in and reducing the quality of your work can help strengthen that stereotype. Which also fits in with testers doing the minimum to get by. Breaking one stereotype can help debunking the other stereotype.. at least in regards to yourself.
NEVER cut corners.
This is something that will help you be a much more reliable and consistent tester but can also be massively influential in helping you to stand out. This can be tied closely with the above point about pushing back, If you feel there is a situation where you feel that you are being rushed, it’s a perfect opportunity to use this tactic. Make it clear that you need more time to be confident with the feature or release. Although the initial feedback may feel negative, be confident in the fact that overall you will be seen as a tester who cares about the product they are working on.
Engage with other members of your team
I really really hate abstract vague answers to specific questions so I’ll try my hardest to keep this point clear and concise. I’ve been asked many times in my short career how I would deal with a difficult developer; if there were loads of bugs in his or her code. My answer is always the same. if I haven’t built up a good enough relationship with a developer beforehand then it’s my fault and I’ll have to deal with the consequences.
I would suggest casually popping over to the developers in your team before a feature has been handed over to QA. Have a brief 5-minute chat about what’s being implemented and what kind of things you may look out for when testing. Bring up the test criteria and see if the developer has some idea regarding the testing. Raise any issues you think may be challenging when they eventually make their way to the test.
Also, ask how the developer may have already tested or considered testing the feature.
Once the story or feature has been handed over to you, continue to engage. Before closing the story have a 2-minute catch-up regarding things you have covered and things you have not. I wouldn’t say do this for every story but I would say do it with a few per sprint. Picking stories that are being done by different developers can also help.
