.png){kind=small}
Manual QA is changing: it’s more than clicking; it’s about knowing what to question
Manual QA is sometimes viewed as a straightforward process: follow the test case, check the expected result, and report anything that does not work.
That picture of manual testing is becoming outdated.
Modern software is more connected, user journeys are more complex, and releases happen faster. A manual QA tester often does much more than check whether a feature works as expected.
They look at how the product behaves, how different parts of it interact, and whether the experience makes sense from a user's point of view.
The value of manual QA is not simply in executing tests. It is in knowing what to question.
A passing test does not always mean a good product
Consider a booking application.
The search works. The user can select a date, choose a service, make a payment and receive a confirmation. Every step in the test case passes.
But what if the user has to go through several unnecessary screens to change their booking? Or the confirmation message is unclear? Or an important option is difficult to find?
The functionality may have passed the test, but there could still be a quality issue.
This is one of the areas where manual testing adds value. A tester can look beyond the expected result and consider how the complete journey behaves from a user's perspective.
Test cases are a starting point, not the whole test
A test case usually describes something the team already expects to happen.
For example:
“Verify that a user can reset their password.”
A manual QA may start there, but the testing does not necessarily end when the password is successfully reset.
What happens if the reset link expires?
What if the user requests several links?
What happens when an old link is opened?
What if the process is started on one device and completed on another?
These questions can uncover scenarios that were never included in the original test case.
This is where exploratory testing becomes useful. It allows QA teams to investigate the product beyond predefined scenarios and follow unexpected behaviour as it appears.
For a deeper look at this approach, see Exploratory Testing in the AI Era: Looking Beyond Generated Test Cases.
The difficult part is not always finding a defect
Not every unexpected result is a software defect.
A test may fail because of an unstable environment, incorrect test data, a third-party service or a misunderstanding of the requirement.
A manual QA may need to investigate what actually happened before raising a defect.
That means considering:
Can the issue be reproduced?
Is the behaviour different from the requirement?
Does it affect other parts of the application?
Is the problem limited to one environment?
What impact could it have on users?
Good manual testing is therefore not just about finding more defects. It is also about understanding the defects that are found.
Manual QA and automation have different strengths
Manual testing and test automation are sometimes presented as competing approaches.
In practice, they can serve different purposes.
Automation is well suited to repetitive and predictable checks. Regression tests, repeated validations, and large test suites can be executed consistently and frequently.
Manual QA can focus more attention on areas where investigation and judgement are important, such as new functionality, changing requirements, unusual user behaviour and exploratory scenarios.
The question is not always “Should this be manual or automated?”
A more useful question can be: “What is the best way to test this part of the product?”
Understanding which tests should be automated and which still benefit from human investigation is itself an important part of modern QA.
Our approach to automation explores this balance further in The QA Approach to Utilising Advanced Automation Tools.
Knowing what to test matters as much as testing it
A software product can have hundreds of possible scenarios. Testing all of them may not always be practical within a release cycle.
This makes prioritisation important.
A manual QA may give greater attention to:
Critical user journeys
Recently changed functionality
High-risk areas
Integrations between systems
Features with a history of defects
Scenarios that could have a significant impact on users
The goal is not to test everything in exactly the same way. It is to spend testing effort where it can provide the most useful information about product quality.
Manual QA has evolved
The role of manual QA has changed as software development has changed.
It is no longer simply about moving through a checklist and marking scenarios as passed or failed. It involves looking at the bigger picture, questioning assumptions and investigating behaviour that may not have been anticipated.
A test case tells a QA what to check. It does not always tell them what else they should look for.
Automation can repeatedly validate known behaviour. Manual QA can investigate the behaviour that still needs to be understood.
That is why modern software testing is not about choosing between manual QA and automation. It is about using the right approach for the product, the risk and the situation.
Comments