Risk-based testing: check your scores against escaped defects
Take a QA lead whose team uses risk-based testing to plan each sprint. Every story gets a risk score, the team tests the high scorers first, and the low scorers…
You have read this

In the dynamic world of software testing, it's easy to focus solely on the technical aspects – finding bugs, writing test cases, running automation scripts. While these are undoubtedly important, what truly makes a software tester stand out in the eyes of their manager? There are seven primary characteristics that a software testing managers wants and value in their employees. These qualities can be thought of as quality characteristics for people. Understanding and developing these traits is key not just to performing well, but also to paving the way for promotions or landing your next testing job.
Let's delve into these 7 essential qualities:
1. Competence
At the core, a software tester needs to be competent. But competence isn't just about knowing how to test; it's about the ability to apply your knowledge in varying situations. This encompasses a broad range of skills, including testing knowledge itself, project management, development skills, business analysis, and even diplomacy. Being an effective tester means leveraging everything you've learned and applying it specifically to the current situation or project you are working on.

Competence also involves a commitment to continuous learning. Without a willingness to learn, technology, testing techniques, and tools will inevitably pass you by, making you less valuable and less flexible. This learning shouldn't just depend on formal training arranged by your manager. It requires proactive effort: reading software testing articles, attending webinars and conferences, talking to peers in the industry, and generally absorbing what's happening in the broader testing world. This self-directed learning is particularly crucial if you've been with the same organization for a long time, as it's easy to become stagnant in your knowledge and feel overly "safe". The world is constantly changing, and you need to stay informed about both new and interesting developments, as well as things that might be new but foolish. Sharing what you learn and bringing new ideas back to your manager is also valuable, as they are likely also struggling to stay current.
Furthermore, competence extends to being willing to teach others. If you've acquired knowledge about a new testing technique, share it. Show how it can be applied. This could involve teaching business analysts (BAs) and developers how to use tools like decision tables, or discussing concepts like DevOps with developers to explore implementing continuous integration or collaboration on test automation. Your career is something you need to actively plan to build and grow.
2. Good Communication — Always
Good communication is often discussed and frequently appears in performance reviews as an area needing improvement, but what does your manager truly need from you in terms of communication? Fundamentally, your manager needs to be sure you will raise important issues or risks rather than assuming others will notice them too. Just as you would report your symptoms to a doctor, a project has symptoms of problems that need to be raised so that everyone is aware and can address them. Don't assume a brewing problem is already known; it might not be. As a tester on your project or assignment, you are the "eyes and ears" of the testing team.
However, effective communication also involves knowing when to speak and when to remain silent. Complaining about known issues that cannot be fixed, such as a tight schedule, is unhelpful. It's important to raise the issue, ensure it's understood, and then focus on doing your job to the best of your ability. Testing managers routinely handle difficult problems, and constant nagging doesn't help; it tends to make the manager see you as part of the problem rather than part of the solution.
Knowing who to raise an issue to is also critical. If you are unsure, ask first. Some managers (project or development) can be very sensitive or reactive. In such cases, it might be better to let your testing manager raise an issue, especially if it's controversial. When in doubt, always ask.
Finally, communication includes effective reporting. If you are asked to provide a weekly status report, do it consistently. This report is an opportunity to remind your boss regularly of your contributions and the quality of your work. Formatting your report exactly as your manager prefers makes it easy for them to use (e.g., cutting and pasting into department reports) and ensures the information is worded appropriately. This simple act of consistently providing well-formatted status reports can be an easy way to gain favor with minimal effort.
3. Independence
Independence can be a challenging trait to balance. While managing issues on your own can be beneficial, it can also backfire if something you thought was under control suddenly isn't. If you've ever heard a manager ask, "Why didn't you tell me sooner?", you might be trying to be too independent. Alternatively, you might have the right level of independence but failed to inform your manager that you were already handling an issue.

What managers really want is to see you trying to handle situations and problems, but simultaneously keeping them informed. Your manager might be able to offer advice or simply sympathy, but they do need to know what's happening. The problem you perceive could be a symptom of a larger issue that requires management-level intervention. Either way, keeping your manager informed provides an opportunity for guidance and potential "air cover" before you fully dive into an issue, which could potentially create other problems.
The source provides a specific example: a tester dealing professionally with a rude or abusive development manager. The tester handled the situation professionally by avoiding open conflict, which was the correct approach. They also appropriately vented their frustration to their testing manager. Allowing the management team to handle personnel issues like this through appropriate layers is crucial. By avoiding direct conflict, the tester gave the management team time to address the problem. By keeping the manager informed, they provided necessary information for personnel action. This professional handling of a bad situation earned the employee the manager's respect.
Independence is a positive sign; it demonstrates growth, a willingness to take responsibility, and readiness for advancement. However, it is also risky. The key is to use good judgment and, when uncertain, to ask for guidance.
4. Honesty
Everyone makes mistakes in their software testing careers; it's part of growing and learning. What a good manager wants and needs is honesty. Your manager is typically on your side. If you've made an honest mistake, it's acceptable because everyone does. The important thing is to work together to figure out the solution. The worst approach is trying to hide a mistake and hoping it won't be discovered. Instead, admit it and move forward. The best managers are those who understand mistakes and help employees rectify them, and this level of understanding and encouragement should be passed on.
It's important to distinguish between different types of mistakes. If a mistake causes significant issues but was well-intentioned, working together is vital for recovery. However, if a mistake was intentional, it represents a completely different problem. Therefore, always ensure your intentions are good, as you will eventually make a mistake and need to seek understanding.
5. A Sense of Adventure
The best testers approach each project as a new and exciting challenge. The root of this "sense of adventure" is maintaining curiosity about the software, the project, the developers, other stakeholders – essentially, everything related to the project. Finding this level of interest contributes significantly to job satisfaction. Nothing motivates you as effectively as genuinely enjoying your work. If you find satisfaction in exploring how you can "break" the software, you will likely enjoy the work. Similarly, if you are happy collaborating with a team to create a high-quality product, getting up for work in the morning becomes easier. This sense of adventure is also what helps you power through the necessary boring or monotonous parts of the job. Tasks like regression testing (which ideally should be boring) or writing test cases can sometimes be tedious, but the excitement of finding bugs ("breaking stuff") and the reward of seeing the software improve balance this out.

Managers prefer to hire people who are self-motivated because they tend to be happier. Self-motivated individuals don't need constant external validation; they recognize when they've done good work, and that recognition fuels their motivation. It's important to be realistic, though. Software testing isn't always fun and games. There are bad times, boring times, and frustrating times. Understanding that these are also part of the job, just like discovering a significant bug just before release, is crucial. Ideally, the job should offer a balance that keeps it interesting and enjoyable overall.
6. Adaptability

Adaptable testers are often the most valued. Managers appreciate employees they can move between projects as needed, knowing they will quickly grasp the new project and get started. This means being able to learn quickly and adjust to any project situation. The more comfortable you are with different software development lifecycle models, the more attractive you are to a manager. Similarly, proficiency in various technologies and tools makes you highly desirable. Knowing test automation skills is also a significant plus.
Flexibility in assignments and the ability to adapt to project situations are critically important in the testing industry. You will never know everything required on a new project from day one. The key is whether you can adapt, are willing to learn, can comfortably navigate the initial period of being unfamiliar, and enjoy the challenge this presents. If you possess these traits, you are likely to succeed in a testing organization and be highly attractive to hiring managers.
7. Initiative
Initiative overlaps with several other qualities, but a good tester demonstrates it clearly. This means finding things that need to be done and doing them without being asked. It involves filling your slack time – periods when you might have completed your assigned testing tasks – with productive activities. These tasks could include creating new reports, organizing testing artifacts into a database, or other improvements. A tester with initiative always finds something productive to do.
If, exceptionally, you genuinely cannot find anything to do, the initiative is to ask your manager for tasks. Managers often have a backlog of tasks they haven't gotten to and welcome help. The source notes that their own team shows such strong initiative on their projects that their plates are already very full.
You should rarely, if ever, be bored. If you are, you are likely not looking hard enough for interesting tasks. If regression testing feels tedious, perhaps you should explore test automation. If the requirements seem unfinished, consider using decision tables to help define them better. Initiative involves actively looking for ways to improve the project and its work products. It also means seeking new things to learn and ways to expand your skills.
Translating Qualities into Career Advancement
You likely already possess many of these traits. If you are reading this, you clearly demonstrate initiative and a drive to improve your competence. The question then becomes how to leverage these qualities for a promotion or a new job.
For a promotion within your current organization, revisit these characteristics and make sure your manager is aware that you embody them. Without being overly pushy, mention these contributions in your weekly status reports. This regular reminder helps the information stick with your manager. Also, ensure you reference your positive characteristics during your performance appraisal discussions. Testers sometimes rely too heavily on bug counts alone to demonstrate their value and fail to highlight the other good things they do. Get noticed for these positive actions.
When interviewing for a new software testing job, a skilled interviewer will probably touch upon all these characteristics. Be prepared to provide specific examples demonstrating how you have exhibited each one. If the interviewer doesn't bring them up, make sure you do. Always talk in terms of concrete examples, as this is much more credible than simply stating you possess a quality. For instance, saying you are adaptable is less impactful than giving examples of situations where you had to prove your adaptability.
Ultimately, managers actively look for these characteristics. Focusing on developing and demonstrating these traits will not only make you a more valuable employee but will also likely increase your job satisfaction. Making a checklist of these seven qualities and reviewing it monthly can help ensure you are actively working to grow, learn, and expand your independence. By doing so, you will become a better employee, and your testing manager will certainly take notice.
Take a QA lead whose team uses risk-based testing to plan each sprint. Every story gets a risk score, the team tests the high scorers first, and the low scorers…
You have read this