UI testing · Expert UX review Available now

One screen. Three browser engines.

Run cases in Chromium, Firefox, and WebKit. Failures include screenshots, replay videos, and logs. Experts use the app to review flow issues that cases cannot catch.

Request a demo Talk about managed QA

The platform runs UI validation; Managed QA experts perform UX reviews.

Browser matrix

Run and assess each engine separately.

Each case runs independently in all three engines. If payment amount validation fails only in Firefox, that failure stays attached to Firefox and is not mixed with passes in other engines.

Chromium, Firefox, and WebKit run by default.
Choose smoke, regression, new feature, pre-release, permission, or other run types.
Run automatically on pushes and PRs matching repository, branch, and changed-path rules, with approval gates when needed.
Reliability is measured per engine. If a result flips in at least 20% of the last 20 runs, the case is quarantined only in that engine.

Run #48 · Pre-releaseTrigger: PR · Approved by QA lead

48 / 48

Cases	Chromium	Firefox	WebKit	API
Session expiry after login
Payment amount validation
Block access to another branch's orders
Order list pagination Quarantined · 25%
24-hour order cancellation rule
Immediate points refund

1 failed · Minor · 3 evidence types

Failure evidence

Replay the moment a screen fails.

Every failed case automatically captures a screenshot, a replay from start to failure, and execution logs, along with the engine and step involved.

Screenshot — Capture the screen at the failed step.
Replay video — Replay the exact sequence of clicks and inputs.
Logs — Attach execution logs for each step.
Evidence is bundled into an HTML report and retained in execution history. It is also linked when you create a Jira issue.

Firefox 131

Order payment

Order amount

KRW 10,000,001

Payment method

Corporate card

Pay now

No limit-exceeded message

Failed · Minor · 1440×900

00:14 / 00:24

14:02:11click #pay-submit
14:02:12expect text Limit-exceeded guidance → Missing
14:02:12screenshot saved · step-07.png

ScreenshotReplay video 00:14214 log linesFirefox 131 · 1440×900

Expert UX review Optional

People find what cases miss.

Passing cases can miss a dead-end after a failed payment or filters that reset on refresh. Before release, experts use the app along real flows and record findings with severity.

Exploratory QA — Walk through key flows using requirements and the collected screen inventory.
Review notes — Record location, reproduction steps, and severity: critical, major, minor, or trivial.
Act on findings — Convert findings into regression cases and create Jira issues when needed.
Release notes — Deliver notes to the owner alongside the verdict.

Talk about managed QA

Checklist categories

What screen cases cover.

These items from the 17-category common checklist directly concern screens. Checklist coverage records whether each category has checks backed by execution.

Input validation

Check that amount limits, required fields, and format errors show guidance and block submission.

Navigation

Check that state and screens remain correct after back navigation, refresh, and direct URL access.

Responsive UI

Compare screenshots across resolutions to find hidden or overlapping elements.

Accessibility

Check that users can complete flows with a keyboard and that labels and focus order are correct.

Localization

Find missing text and broken layouts after switching languages.

Error handling

Check that failed responses leave the screen usable and guide users to their next action.

Frequently asked questions

Before starting UI validation and UX review

What do we need to start UI validation?

Provide a target URL, preferably staging, and test accounts, then collect screens. Collection explores the site and builds a screen inventory within 90 seconds to inform case generation.

Do we need to run all three engines?

Cases run in Chromium, Firefox, and WebKit, with the run type set in automation rules. Passes, failures, and quarantine are recorded per engine so one engine's issues do not obscure the others.

Are UX reviews automated too?

No. Managed QA experts perform UX reviews by using the app directly. We agree on scope and cadence during onboarding. Notes and findings connect to cases and release notes within the same platform.

What happens to tests with inconsistent results?

We track result flips on the same commit over the last 20 runs. At a 20% flip rate, checks are automatically quarantined. They continue to run and report results, but cannot cause a FAIL verdict; the run is marked CONDITIONAL.

What if we already have UI test code?

Connect your repository and code-based generation reads existing tests and screen code to draft cases. Once approved, they use the same three-engine execution, evidence capture, and release verdicts.

Three engines.
One view of the results.

See how results from three engines, failure evidence, and expert UX notes come together in one release verdict.