Autonomous Software Testing: What the AI Agent Should Decide
Autonomous software testing is testing in which an AI agent plans, writes, runs, and repairs tests with little step-by-step direction, exploring the application, choosing what to check, and acting on the results, while people set the goals and approve any decision that changes what the product is expected to do.
That last part is where most teams get stuck. An agent that can do every step can also make every decision, including ones that hide a real bug. This guide sorts the decisions in testing into three groups: what the agent can decide alone, what it should propose for a person to approve, and what stays with people. For a hands-on setup with one agent, see our guide on how to use Claude Code for QA automation.
We build Test Studio, an AI test automation platform with its own agent, so we have a view on where the lines sit. To ground that view, we installed Playwright's test agents on Playwright 1.63 and read the instructions they ship with.
What is autonomous testing, and how is it different from test automation?
Autonomous testing differs from test automation in who makes the decisions. In classic test automation, people decide what to test and write every step, and the tool only runs it. In autonomous testing, an agent makes many of those decisions itself.
Approach | Who decides what to test | Who writes the steps | What happens when a test fails |
|---|---|---|---|
Scripted test automation | People | People, in code or a recorder | A person investigates and fixes it |
AI-assisted test automation | People | AI drafts, people edit | AI suggests a cause, a person fixes it |
Autonomous software testing | The agent, within goals people set | The agent | The agent investigates and proposes or applies a fix |

The jump from the second row to the third is not only about speed. It moves judgment from people to the agent. That is useful for routine judgment, such as finding a renamed button, and risky for judgment that defines correct behavior, such as what a discount should total.
Which decisions does an autonomous testing agent make?
An autonomous testing agent makes decisions in every step of the testing work, not only in writing code. Listing them is the first move toward deciding which ones to hand over.
What to test. Which pages, flows, and states to explore, and which risks matter most.
What counts as correct. The expected values and messages each test checks against.
How to find each element. Which locator to use for each button, field, and message.
When and where to run. Which tests run on which change, browser, and environment.
What a failure means. Whether a failure is a real bug, a broken test, or an environmental problem.
What to do about it. Whether to repair the test, retry it, skip it, or report a defect.
What goes into the suite. Whether a new or changed test is merged into the shared suite.
Some of these are mechanical. Others decide whether a bug reaches your users. The next two sections split them.


