found a qa team that automated 80% of regression last year.
now leadership wants to cut the team in half.
"AI does it now"
no. AI runs the scripts. humans still decide what to test.
confusing the tool with the judgment.
found a forecast: AI test automation market hitting $36B by 2032
the number is real. the hype around it isn't.
most teams still can't write a stable test without it flaking on CI.
market size ≠ problem solved.
1/6 Everyone's calling agentic AI a "paradigm shift" for QA. Maybe. But I've seen enough hype cycles to know the gap between the press release and the production environment.
5/6 We started writing about EvalOps because testing AI outputs is genuinely different from testing deterministic code. There's no "expected result" when the system reasons its way to an answer.
6/6 So yes, AI is changing QA. But the teams treating that as "less testing needed" are the ones who'll have the most interesting post-mortems.
Ten years running QAwerk. The tools change. The need for someone who actually checks the work never does.
1/2 "QAwerk team has been of enormous help in improving the quality of our releases at Kazidomi. They are communicative and highly professional, with a proactive attitude.
2/2 The automated and manual testing work we did with them was delivered to a high standard, and we’ve become trusted partners."
-- Benjamin Stuart, Product Manager at Kazidomi
More client stories: qawerk.com/testimonials/
1/9 Every few months a new article drops declaring AI has finally "solved" software testing. 2024, 2025, now 2026.
At QAwerk, we've spent the last year actually running these tools on real client projects. Not benchmarks. Real codebases, real deadlines, real bugs.
8/9 Ten years running QAwerk, we've watched every wave of "this will automate QA." Codeless testing, record-and-playback, model-based testing. Each one moved the floor up. None of them replaced judgment.
found a bug last week that passed every test
AI wrote it. looked clean. compiled fine.
failed in production because it had no idea how the rest of the system behaved
green tests aren't the same as correct code.