Can an agent do QA testing?
Yes. Writing tests, running regression suites, driving the browser and reporting reproducible failures is dependable agent work, and it removes the manual regression pass that everyone hates and eventually skips.
- Hours back per week
- 12
- Human cost
- €3,000–5,500/mo per QA engineer
- Agent cost
- €40–150/mo
Step by step
A job is never one task. Here is each step, rated on its own — tick the ones you would actually hand over and take the brief with you.
Write test cases from a spec
YESIncluding the edge cases the spec did not mention.
Automate browser flows
YESAnd repair them when the UI changes, which is where most test suites die.
Run regression before release
YESEvery time, in full, rather than the abbreviated version at 6pm on a Friday.
Report bugs properly
YESReproduction steps, environment, video, expected versus actual. Better than most bug reports.
Exploratory testing
MOSTLYIt tries unusual paths. It lacks the instinct for where a specific team tends to break things.
- Yours
Decide it is ready to ship
NOT YETShipping is a risk decision with a name attached to it.
4/5 steps selected. Build a brief scoped to exactly those, with the guardrails for this job attached.
What still needs you
- The release decision
- Judging severity against business risk
- Usability judgement
How this goes wrong
Tests written against current behaviour rather than intended behaviour. The suite goes green, the bug is now enshrined, and the failure is invisible until a customer finds it.
What it needs access to
- Test framework
- CI
- Staging environment
- Issue tracker
- Browser automation
Read access to all of it, write access to as little as possible. Scopes are enforced by the system; instructions are only followed by the agent.
The prompt
A full brief for this job, written the way it should be given: explicit about what to do, and more explicit about what not to.
You are my QA agent. For each new feature, write test cases from the spec covering the happy path, edge cases, and error states — then tell me which requirements in the spec are too vague to test, because that is usually where the bugs will be. Automate the critical user journeys and keep them passing when the UI changes. Run the full regression suite on every release candidate and report results with pass rate and any new failures. File bugs with exact reproduction steps, environment, a video, and expected versus actual. Never modify application code to make a test pass. Never sign off a release.
Questions people ask
Can it test without existing test infrastructure?
Yes — it can drive a browser directly and report what it finds. That is the fastest way to get coverage on a product that has none, though a real suite is still the destination.
Want this one actually running?
The brief above is the easy half. The other half is connecting it to Test framework and CI, holding it inside the boundaries on this page, and having somewhere the exceptions land where you will actually see them. That is what Ogento does.
Set up a QA testing agentThis site is made by Ogento. The verdicts are not written to suit them — 32% of the jobs here say do not hand this over wholesale.