
Here’s how I run a full QA round in a morning without a dedicated QA tool.
You don’t need a dedicated QA tool to let AI test your product.
Last week I ran five QA rounds on a SaaS product. 80+ test cases. 15+ bugs found and fixed. In one day.
The setup is three tools you probably already have.
🎯 What the setup looks like
1: Claude writes the test suite. You describe what needs testing in plain English, as if briefing a colleague. The prompt can be as simple as: “Create a set of test cases for my product XXXX that I can hand to Cowork. Cowork should then send reports back, so Claude Code or my team can fix what it finds.”

2: Cowork, Anthropic’s browser agent, opens the product in a real browser, logs in, clicks through every flow and returns a report with PASS/FAIL and screenshots. You need the Chrome plugin installed. Quick guide here.
3: Claude Code receives the report and fixes each bug directly in the codebase. A fresh test round verifies the fixes hold. Or pass it on to your team.
That’s it.
🛑 The interesting part is what the agent finds
A button that technically “works” in the code but is blocked by a DropdownMenu swallowing click events. Race conditions on rapid double-clicks. Missing validation on edge cases like a price of 0.
The kind of thing that first shows up in production on a Friday afternoon. The kind of thing nobody takes ownership of in Monday’s standup.
For you as a product manager, this is not a QA story. It’s a discovery story.
The feedback loop you usually wait for, write tickets, wait for prioritization, debate severity, fix, wait for re-test, doesn’t have to take weeks anymore. It can run in hours.
And when the QA cycle is short enough, it changes which bets you dare to take. Trying a hypothesis becomes cheaper than debating it in a refinement meeting.
Dedicated AI QA platforms exist. QA Wolf, Momentic, Testim. They’re good. But you don’t need them to get started.
👉 Your tip this week
Pick one flow in your product. Login, checkout, onboarding, pick one. Write down in plain English what needs testing. Let Claude turn it into a test suite.
Run it manually yourself the first time and feel how much time it saves. Build from there.
Thanks for reading. Got feedback, thoughts, or something you disagree with? Write to me. I read everything.
Best, Martin