Manual testing is not dying. The manual testing job is shrinking. Those are different claims, and most articles blur them deliberately, because "manual testing will always be needed" is comforting, true, and completely useless if you're the person whose role is being consolidated.
Here's the position I'll defend: the skill of testing by hand is becoming more valuable per hour and required in fewer total hours. A team that once needed five manual testers to get through a regression cycle now needs one strong tester with judgment, plus a suite. Excellent news for the one.
Difficult news for the other four.
What actually changed
Three things, none of them "AI replaced testers":
- Regression execution got automated, slowly, over fifteen years. Not new, not AI — and that repetitive work was the volume employer of manual testers.
- Test artefact production got cheap. Test cases, plans, traceability matrices, a hundred input permutations — an LLM drafts them in seconds at mid-level quality. If your visible output was documents, it just got commoditized.
- Automation got easier to start. Writing a first Playwright test is far less painful than a first Selenium test was. "I can write a basic UI test" stopped being a differentiator.
None of these removed the need to decide what matters. They removed the mechanical work around that decision.
What AI is genuinely bad at
- Knowing what "wrong" means here. A model sees a misaligned button. It doesn't know a 200ms delay on this screen causes support tickets because it's where users enter payment details under time pressure.
- Deciding what NOT to test. The hard skill has always been subtraction. Models produce enormous, undifferentiated suites. Someone has to say "these eleven cases matter, delete the rest" — and be right, and be accountable.
- Testing across the seams. The expensive bugs live between systems: a webhook that fires twice, a timezone that converts wrong, a retry that duplicates an order.
The uncomfortable part
"Exploratory testing is irreplaceable" is true. It does not protect your job.
Exploratory work is high-skill and low-headcount — more valuable, better paid, and there's less of it. Being irreplaceable in aggregate isn't the same as being individually hard to replace.
So what should a manual QA actually do? Not "learn automation" in the
abstract — that advice has failed for a decade because it has no sequence.
Instead:
- Learn one language properly (Python or TypeScript) until you can solve a problem you haven't seen before, not just finish a tutorial.
- Build one real thing — a small framework testing a public site, in a repo you can send someone. It beats any certificate because it's checkable.
- Get technical about the job you already have — read the logs, learn the schema, reproduce a bug via API instead of the UI.
- Use AI as a fast collaborator, not an oracle. Be the person who knows which parts of its output are wrong. That role requires more testing knowledge, not less.
Manual testing as a skill is appreciating. Manual testing as a job title is depreciating. Which one is good news for you depends entirely on whether your value is in the judgment or the execution.
I wrote the longer version of this, plus a full roadmap from manual QA to SDET, at QALadder — free, no paywall.
Top comments (0)