What If You Are the Single Tester in Your Team or Company? [Podcast]
Let's talk about how to calmly approach the task of being the only tester and create an efficient process.
Join the DZone community and get the full member experience.Join For Free
Joel Montvelisky, Chief solution architect at PractiTest — test management tool, and Rob Lambert, Director of cultivated management, a tech consulting company with today's topic: What to do if you are the single tester in your team or company?
- The first step would be to take it easy. Being a sole tester of a company is without a doubt a big responsibility, but panicking won't help here. Your job is to lead the testing process of the company, it doesn't mean you should be the one that performs all the necessary tests. Therefore, not every bug that would be found after releasing the product is your responsibility.
- Figure out what testing is, what does quality mean, what should the testing process provide. Take notice of the process that has been done beforehand.
- Be assertive regarding your decisions. Come to a conclusion about what is the right process for you, get it documented and communicate it for the rest of your team.
- When you start working as a tester in a company, you should understand the existing system. As the new part of the team, you should understand what is expected of you in relation to the team. Every team is different, therefore your role should be performed differently in relation to your situation.
- As the professional tester of your team, it is your challenge to define what modern testing is and communicate it to the rest of the organization.
- Communication and visibility are very important. Don't be afraid to present your workflow and new ideas to the high levels of your organization as well as your other colleagues. The testing process is diverse and constantly changing if you are able to communicate these changes to the high level of the organization, you are on the right track.
- When you start working for the new company, ensure quick wins in order the get legitimacy. Create a checklist for the urgent things to be tested and at the same time start working on things with a high level of importance.
- Create dashboards and metrics for your team. It would help to point out the problematic areas to your developer team as well as show them your workflow.
- Dictate what areas would you be focusing on your testing process to your team, what are you going to test and what are you not. That would help you generate their feedbacks regarding your testing.
- Learn about Exploratory Testing, it is a very good technique when you need to cover things quickly.
- You are never the only tester. You can always use the developers, support team or other people in your team. You can use outsourcing or other companies in order to test your product.
- Work alongside your developers and cooperate with them the all along the process.
- Start the testing process as early as you can.
Published at DZone with permission of Joel Montvelisky, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.