Write a test in plain English.
Run it on any site or API.
QAlchemy reads your BDD scenario, uses an LLM to find its own way through the page, and heals its own locators when the DOM changes — so a moved button doesn't break your whole suite. Same flow drives API tests too.
How it works
Scroll through a run, step by step.
Write plain-English BDD
Given/When/Then, like you always have. No selectors, no page objects, no framework-specific glue code.
The LLM finds its own way
Each step is planned and located against a live snapshot of the actual page — the same step works whether it's Zomato, saucedemo, or your own app.
It heals when the page changes
If a selector stops matching, QAlchemy re-resolves it from the live DOM and updates its cache — instead of failing the whole suite.
Get the full picture
Every run rolls up into a report: what passed, what healed itself, and any BDD gaps a human should take a look at.
One suite, two testing surfaces
The same plain-English BDD flow drives real browser UI tests and raw API tests — pick one, and watch it run.
Less human effort. Lower cost.
What changes when an LLM maintains your selectors instead of a person.
Illustrative, not a benchmark — rough hours per regression suite spent re-reading the DOM and rewriting brittle selectors after a redesign. Your numbers depend on suite size and how often your UI changes.
Compare Traditional testing vs QAlchemy
Built for tests that don't rot
Everything you need to stop babysitting brittle selectors.
Self-healing locators
Primary selectors first, LLM fallback only when they miss — and it remembers what worked, so the fix sticks for every future run.
Live browser view
Watch the run happen inside the page in real time, streamed straight from a headless Chromium session.
Works on any site or API
No per-site step files — the same generic engine plans and locates against whatever page or endpoint you point it at.
Dual LLM fallback
OpenRouter first, automatic Hugging Face fallback on rate limits, with retries baked in.
Smart step caching
Repeated step shapes hit a persistent cache instead of the LLM — a 1,000-step suite doesn't mean 1,000 calls.
Full BDD gap reports
Every ambiguous step the agent had to assume something about is flagged for a human to tighten up.
See it inside the product
Not just a test runner — a board for the whole suite lifecycle, and the numbers to prove it's working.
Organize suites like a project board
Drag suites between To do, In progress, Sent for dev, and Completed — or use the dropdown fallback for keyboard and touch.
Track performance over time
Flaky tests, slowest scenarios, and cache-hit rate trend as your suite grows — not just pass/fail.
Simple pricing
For real test suites
- ✓ Unlimited scenarios
- ✓ Bring your own LLM key
- ✓ Priority self-healing
- ✓ Full BDD gap reports
For QA teams at scale
- ✓ Everything in Hobby
- ✓ Higher concurrency
- ✓ Shared step cache
- ✓ Priority support
For large orgs with custom needs
- ✓ Everything in Corporate
- ✓ SSO & audit log
- ✓ Custom contract & SLA
- ✓ Dedicated support
Questions
No. Describe the step in plain English (or Gherkin/BDD) and the LLM figures out what to click, fill, or assert against a live snapshot of the actual page.