UI testing
Qodex tests web apps the way a user would: it opens your app in a real Chromium browser, explores pages, creates test scenarios from plain-English goals, and records the artifacts you need to understand every pass or failure. You do not need to write Playwright selectors by hand to start. Describe the flow you care about, such as “test signup” or “make sure a user can update billing details,” and Qodex drives the browser, records the intent of each step, and saves the scenario so it can run again later.How UI testing works
The UI testing flow has four parts:- Discover pages by crawling your app and building a Pages catalog with screenshots across desktop, tablet, and mobile widths.
- Create scenarios from natural-language goals, with Qodex resolving each step against the live page.
- Replay scenarios using cached browser actions so repeat runs do not need an LLM call for every step.
- Capture artifacts such as screenshots, DOM snapshots, console logs, network logs, and optional video so failures are easy to debug.
What you can start with
Crawling and the Pages catalog
Let Qodex discover your app’s pages and capture responsive screenshots for each one.
Intent-driven UI scenarios
Create UI tests from user goals instead of brittle selector scripts.
Replay cache and self-healing
Re-run saved scenarios cheaply, with recovery when the UI changes.
Per-step artifacts
Review screenshots and failure evidence for every important browser step.
Why repeat runs stay cheaper
Most AI testing tools ask a model to inspect the page on every replay. Qodex uses the model when a UI step is first authored or when a cached action stops working. In the normal replay path, the saved Playwright action runs directly in Chromium. That means nightly regression runs, scheduled checks, and CI runs scale mostly with browser execution cost. The LLM comes back only when the page has drifted enough that Qodex needs to re-resolve an intent.What you can do today
- Crawl your app and build a Pages catalog with screenshots at desktop, tablet, and mobile widths.
- Author scenarios from chat while Qodex drives a real browser end to end.
- Re-run scenarios with cached selectors so stable flows do not require an LLM call.
- Recover from UI drift when a cached selector no longer matches the page.
- Capture per-step screenshots, and capture DOM, console, and network logs when a step fails.
- Reuse logged-in browser state so authenticated tests do not repeat the login flow on every run.
Where to go next
Crawling and the Pages catalog
See how Qodex discovers pages before it creates tests.
Intent-driven UI scenarios
Learn how plain-English steps become browser actions.
Replay cache and self-healing
Understand how saved scenarios keep working as the UI changes.
Per-step artifacts
Learn what Qodex captures when a UI test runs.