Explaining a software tester’s job may be more difficult than it seems, especially to those unfamiliar with the field. The most intuitive answer would probably be that they check the software for bugs, or as a guest on the “Testing peers” podcast humorously described how she explains it to her parents: “You know when the bank website messes up? I look for those problems”.*
This explanation is not incorrect, but it only scratches the surface. It still says nothing about the full scope of their responsibilities and the cluster of QA-related activities that help companies achieve business goals. Testers carry out a range of diverse tasks and all these contribute to the success of the product.
For a moment, let’s go beyond the basic job description and break down what testers actually do when they test, in an attempt to highlight some less obvious aspects of their role.
Asking questions
To properly test any software product, a QA expert needs to have the right insights into its intended functionality, design, and usage. Understanding the system implies understanding the technical details, but also the broader context, namely the system’s purpose and potential impact.
It’s key not to assume anything in advance. Testers should leave no stone unturned and actively seek information from developers, domain experts, product owners, business analysts, users, and other sources. Proactively asking probing and inquisitive questions should be a tester’s standard routine and ideally even a character trait.
Uncovering new information
A tester’s job is not unlike detective work. It involves asking questions, but it also involves independent investigation, in which a tester basically “asks questions” to the system itself.
They analyze code and system behavior to identify potential risks and ensure that the software meets quality standards. They explore how the software functions under various conditions and scenarios to identify potential hidden bottlenecks, vulnerabilities, and performance concerns. A critical part of the tester’s job is coming up with different creative approaches to test the system’s capabilities and resilience in order to uncover new valuable info. An open mind and a will to experiment beyond what is given are thus a must for a software tester.
Ensuring quality beyond mere functionality
Furthermore, a tester should never be happy with the mere fact that the system is operational. It’s crucial to keep in mind factors like speed, performance, UX, or any other criteria that are valuable for the software’s purpose.
First, they need to understand (or in fact establish) a set of criteria that determines which behavior the system must exhibit to be considered acceptable. Then, they detect and report any friction or obstacles that hinder smooth interactions with the software to make it not just functional but also straightforward and user-friendly.
Walking in the user's shoes
Testers should not only understand the needs and pain points of the user, they need to try to think like a user and focus on the user’s expectations from the system. This user-centric approach enables the identification of usability issues that maybe wouldn’t have otherwise seemed problematic to a tech-savvy QA engineer, such as confusing interfaces or difficult navigation.
Moreover, walking in the user’s shoes enables a QA expert to explore a wide array of scenarios, experiences, and demands a user could have when interacting with the program. This may include use cases that were not outlined in the test specification or product documentation at all, because users don’t always interact with the system the way developers predicted.
Communicating with stakeholders
When it comes to communication, it goes two ways. Testers don’t just ask questions about requirements and user expectations; they also provide reports and feedback for various stakeholders, including developers, product managers, and customers.
Achieving efficient communication in this case is no easy feat. Different stakeholders need different types and amounts of info, and they also possess different levels of expertise. Summarizing the results for each and every one of them demands a constant shifting of perspectives and a continual search for the right balance between being overly general and too detailed in communication. In general, testers should contribute to an open, collaborative environment, encouraging transparency throughout the software development lifecycle.
Weighting risks and prioritizing efforts
Just like any other phase of SDLC, testing operates inside limits set by the project leads and in accord with the business needs. Software testing is a dynamic process, and testers often face the challenge of conducting comprehensive testing while respecting project constraints. They prioritize their efforts based on project timelines, resource availability, and critical functionalities.
Sometimes, in order to meet the time constraints, they must determine which features are instrumental to the system and then focus all their attention on testing these features. This can be a tough decision, and it must be based on solid methodology and knowledge of the system. For this reason, there are various risk-based testing methodologies that make sure all critical aspects of the software are thoroughly tested and ready for deployment within reasonable deadlines.
Closing remarks
All in all, a tester’s job includes many different tasks and responsibilities, and requires a deep understanding of the client’s business, the market, and the system in question. At Sixsentix, we are proud of our pool of top-notch QA consultants who are channeling their knowledge and expertise into solutions that help our clients achieve top software quality.
For more info, check out our Solutions pages, or reach out to our team.
*Note: This blog post was inspired and influenced by a very neat podcast session of “Testing peers” with the same title - “What do testers do?”. We recommend listening to it for valuable insights on some subtle, but crucial elements of software testing.