Is there any lock-in?

No. The output is standard Playwright .spec.ts that runs with npx playwright test. If you stopped using Validate.QA tomorrow, your tests would keep working.

Can I edit the generated tests?

Yes. They're plain code in your repo. Edit them like any other test — and Validate.QA can still run and heal them.

The tests you get

Standard @playwright/test .spec.ts you own and run with npx playwright test — no DSL, no SDK, no lock-in.

Validate.QA doesn't generate steps in a proprietary format or lock your tests inside a dashboard. The output is ordinary Playwright code — the same code an engineer on your team would write by hand, except proven against your app before you see it.

You own the code

Standard @playwright/test — no custom runner, no DSL to learn, no SDK to import.

Runs anywhere Playwright runs: npx playwright test, your machine, your CI, your containers.

Committed to your repository (or exportable), so the tests are yours even if you stop using Validate.QA.

What a generated test looks like

Locators are chosen with a stability-ordered strategy (test-id and ARIA role first, raw CSS last), and assertions are written from what the app actually did — then verified against the live DOM before the test is promoted.

A generated UI spec — role-based locators and a meaningful assertion

API tests, too

From the same exploration, Validate.QA builds Playwright API tests using the request fixture — chaining real calls (authenticate, create, read, delete) observed from your app's traffic, with assertions on status and payload.

A generated API spec — a dependency chain from observed traffic

Open The tests you get · Get Started Free