Selenium gave us browser automation. agent-qa adds intent, self-healing, and memory.

Selenium is the two-decade veteran of programmatic browser control. agent-qa is what the same job looks like now: plain-English tests, adaptive execution, and a harness built for coding agents.

Try agent-qa, the open-source AI QA agent that remembers what a decade of scripts never could.

Get Started Explore Live Demo

agent-qa vs Selenium

Capability	agent-qa	Selenium	Details
Plain-English authoring			Selenium tests are code plus locators plus explicit waits. agent-qa tests are natural-language YAML anyone can review.
Survives UI changes			XPath and CSS locators are Selenium's most famous failure mode. agent-qa re-plans from intent when the UI shifts and remembers the change.
Execution memory			agent-qa accumulates behavioral memory across runs; Selenium sessions know nothing about the last run.
Open source			Both are open source. agent-qa adds the AI harness on top of open foundations.
Local and CI execution			Both run anywhere. agent-qa needs no Grid topology to plan, execute, and report a flow.
Mobile app testing			Selenium's ecosystem reaches mobile through Appium as a separate stack. agent-qa covers web and native mobile in one contract.
Coding-agent native			agent-qa exposes MCP tools, Skills, artifacts, and failure classification designed for autonomous agents; Selenium predates the idea.
Wait/timing management			Explicit and implicit wait tuning is a Selenium discipline of its own. agent-qa's runtime observes actual app state while executing intent.

Why teams retire Selenium suites for agent-qa

Decades of locator debt, gone

Legacy Selenium suites are archaeology: brittle XPath, page objects three refactors behind, waits tuned for servers that no longer exist. agent-qa lets you re-express what those tests were for — in English — and delete the debt instead of servicing it.

The team that can write tests gets bigger

Selenium coverage depends on engineers fluent in the framework. agent-qa tests are plain-English YAML — product engineers, QA specialists, and coding agents all author at the same speed, so coverage stops bottlenecking on framework expertise.

A harness from the agent era

Selenium was designed for humans writing scripts against browsers. agent-qa is designed for a world where coding agents change code continuously and need to verify it themselves — MCP tools, Skills, memory, and evidence built in from the start.

Selenium earned its place in history. agent-qa is what you'd build today: open source like Selenium, but with intent instead of locators, memory instead of amnesia, and coding agents as first-class operators.

Frequently asked questions

Is agent-qa a good Selenium alternative?

Yes — it's the generational upgrade path. agent-qa replaces locator-based scripts with natural-language tests that self-adapt, remember prior runs, and produce reviewable evidence, while staying open source and repo-owned like the Selenium workflow you're leaving.

What does agent-qa cost compared to Selenium?

Both are free and open source. Selenium's hidden cost is the engineering time spent maintaining locators, waits, and Grid infrastructure; agent-qa trades that for LLM token spend under your control, with caching to keep repeat runs cheap.

How do I migrate a large Selenium suite to agent-qa?

Don't port code — harvest intent. Group your Selenium tests by user journey, write each journey as one agent-qa YAML test, and run both in parallel until trust is established. Teams typically find hundreds of scripts collapse into dozens of intent-level tests.

Does agent-qa need Selenium Grid or similar infrastructure?

No. agent-qa runs against local browsers, CI runners, and mobile emulators or devices you already have — there's no hub-and-node topology to operate, and no vendor cloud in the loop.

Can agent-qa test legacy web apps that Selenium currently covers?

Yes. agent-qa drives real browsers, so server-rendered and legacy UIs work the same as SPAs — often better than old Selenium scripts, because intent-based execution doesn't depend on the exact markup those scripts froze in time.

Write tests in natural language

Define actions and assertions in human language while agents work from visible roles, labels, and screen state.

Learn about natural language tests

tests/linear/create-issue.yaml

test-id: t_slice-cart-bane-deep-fold-prim-paar-baru-nable-kayname: Check Linear issue creation flowtarget: linear-webuse:  browser:    name: chromiumsteps:  - Click on the Create issue icon.  - |    Verify that the Create issue modal    is shown.  - |    Enter "Fix mobile login" in the    "Issue title" input field.  - |    Select "Engineering" from the Team selector and select "Todo"    from the Status field.  - Click on the Create issue button.  - |    Verify that the created issue is shown with title "Fix mobile login"    and status "Todo".

Check Linear issue creation flow

Step 1 of 65.0s
Click on the Create issue icon.
#1click4.8s
Step 2 of 64.1s
Verify that the Create issue modal is shown.
#1assert4.0s
Step 3 of 65.3s
Enter "Fix mobile login" in the "Issue title" input field.
#1fill5.1s
Step 4 of 66.2s
Select "Engineering" from the Team selector and select "Todo" from the Status field.
#1select3.0s
#2select3.0s
Step 5 of 63.4s
Click on the Create issue button.
#1click3.2s
Step 6 of 65.8s
Verify that the created issue is shown with title "Fix mobile login" and status "Todo".
#1assert5.6s

Evolves with every run

With every test run, agent-qa builds execution memory from product, suite, and test observations, then adds that context to future runs. agent-qa also curates memory from steps that were healed during execution, helping future runs avoid the same mistake.

Learn about memory

Memory - Notion

obs_ria-gue-cake-long-elf-wag-time-quad-profit-alf

Workspace navigation contract

trust 0.91|confirmed 6 times

last confirmed today

Sidebar groups stay visible after switching between Docs, Projects, Calendar, and Settings. Future runs should verify the workspace switcher, command palette, and primary navigation labels before attempting deeper page assertions. This prevents the agent from rediscovering the navigation model on every run and keeps later assertions focused on the actual page behavior.

obs_mara-scope-desk-calm-page-search-index-round-quiet-latch

Command palette search context

trust 0.87|confirmed 5 times

last confirmed yesterday

The command palette returns workspace-scoped results first, then recent pages. Repeated tests should search for stable page titles and avoid assuming that the first result is the same across seeded workspaces. When the palette already contains recent pages, the agent should filter by exact title text before selecting the result.

obs_motif-page-toolbar-active-editor-share-comment-menu-state

Page toolbar persistence

trust 0.83|confirmed 4 times

last confirmed today

The page toolbar appears only after the editor area is active. Future runs should click into the page body before asserting Share, Comments, and More actions. This memory keeps the planner from treating a hidden toolbar as a failure when the page is simply idle.

Built for Humans

Top-tier developer experience with a beautiful dashboard, intuitive CLI, and clear workflows for authoring, running, and debugging tests.

Learn about the dashboard

agent-qa dashboard

Runs

AllRunningQueuedCompletedFailed

StatusTest NameTargetDuration

PassedCheck Linear issue creation flowlinear-web (Web)29s

PassedGitHub release fixture smokegithub-web (Web)41s

FailedSentry issue triage regressionsentry-web (Web)1m 12s

PassedSupabase project smoke testsupabase-web (Web)38s

agent-qa CLI

❯ agent-qa run tests/linear/create-issue.yamlRunning 1 test(s)...✓ Click on the Create issue icon. 5s  Sub-actions: 1 total (1 succeeded, 0 failed)✓ Verify that the Create issue modal is shown. 4s  Sub-actions: 1 total (1 succeeded, 0 failed)✓ Enter "Fix mobile login" in the "Issue title" input field. 5s  Sub-actions: 1 total (1 succeeded, 0 failed)✓ Select Engineering from Team and Todo from Status 6s  Sub-actions: 2 total (2 succeeded, 0 failed)✓ Click on the Create issue button. 3s  Sub-actions: 1 total (1 succeeded, 0 failed)✓ Verify created issue title and Todo status 6s  Sub-actions: 2 total (2 succeeded, 0 failed) PASS  Check Linear issue creation flow 29sRun ID: r_lined-frig-schema-main-depart-hing-aline-balls-cran-dess  Memory: 1 added (3s)Run attributes:  agent-qa.trigger=cli  agent-qa.runner=localTests:  1 of 1 passedSteps:  6 passed, 6 totalCache:  6 hits, 0 missesTime:   29s

Built for Machines

The same primitives are exposed through MCP and skills so coding agents can discover schemas, author YAML, enqueue runs, inspect artifacts, and triage failures.

Learn about MCP

CLI

MCP

SKILLS

Accelerate runs with smart Cache

The action cache reuses validated plans across similar subsequent test runs, reducing planner work, token usage, and runtime overhead.

Learn about caching

Execution Speed

42s -> 8s

Cached action plans skip redundant planner work on similar subsequent runs.

Reduced Token Usage

fewer planner tokens

Validated steps reuse prior reasoning when the flow and screen state still match.

Run sandboxed hooks during tests

Run Node, Bun, Python, or Bash hooks in isolated Docker containers to set up environments, call APIs, seed fixtures, tear down state, or pass structured outputs back into the active test run.

Learn about hooks

hooks - prepare-checkout.ts

// emits CHECKOUT_EUR_TOTAL_CENTS for the active test runconst response = await fetch("https://api.frankfurter.app/latest?from=USD&to=EUR,GBP")const { rates } = await response.json() const fixture = {  plan: "team",  currency: "USD",  subtotal_cents: 2900,  eur_total_cents: Math.round(2900 * rates.EUR),  gbp_total_cents: Math.round(2900 * rates.GBP),  seat_limit: 12,  fixture_at: "2026-05-07T00:00:00Z",} const env = Object.entries(fixture)  .map(([key, value]) => `CHECKOUT_${key.toUpperCase()}=${value}`)  .join("\n") await Bun.write("/tmp/agent-qa.env", `${env}\n`)console.log(JSON.stringify({ checkoutFixture: fixture }, null, 2))

Review your QA like code

Tests, configs, hooks, memory, and suite logic all live as version-controlled code, so every change can be diffed, reviewed, reused, and shared across teams.

Learn about configuration

review - tests/supabase/project-smoke.yaml

diff --git a/tests/supabase/project-smoke.yaml b/tests/supabase/project-smoke.yaml
index 4a31d1f..6af40cd 100644
--- a/tests/supabase/project-smoke.yaml
+++ b/tests/supabase/project-smoke.yaml
@@ -4,8 +4,9 @@
 test-id: t_lumen-rail-civic-model-pager-slate-harbor-fable-drift
 name: Supabase project smoke test
 target: supabase-staging
 steps:
   - Open the Supabase dashboard
-  - Verify the project status reads "Healthy"
-  - Open API settings and verify the project URL is displayed
+  - Open Project Settings > API
+  - Verify the Project URL matches $SUPABASE_PROJECT_URL
+  - Verify the anon key remains masked before copy

Self-healing test execution

When any sub-action, such as click, fill, or select, fails, agent-qa re-observes the UI and tries a different path in the same run. Tests recover from UI drift and flaky interactions instead of failing on the first broken action.

Learn about self-healing

healed run - tests/table/create-row.yaml

Step 11 of 20

Add column "story_name" with type text in the create-table form.

#1click3.9s

#2fill2.8s

#3click3.9s

#4tapCoordinate8.8s

#5click4.6s

#6select6s

#7click4.4s

#8click11.7s

#9keypress13.4s

Bring your own LLM

Run tests with the model of your choice via OpenAI- and Anthropic-compatible endpoints, Gemini, local or open-source models, and subscriptions like Codex and Claude Code.

Learn about LLM providers

More comparisons

* This comparison is based on publicly available information. Product capabilities and pricing can change; verify details with each vendor before making a purchase decision.