Skip to main content
Beta. Test Generation is available to selected customers only. It is not included in any plan, and it is not covered by the TestDino service agreement or support SLA. Behavior and limits can change between releases. Ask for access through Support.
Test Generation records or describes a browser flow and compiles it to a deterministic Playwright spec. Every step is stored as structured data first, so the same test always compiles to the same TypeScript, and you review real Playwright code rather than a recording.

Quick Reference

AI runs only while you author. The compiled spec and every replay are model-free.

Record a flow

Recording runs a headless Chromium on the server and streams it into the browser tab. You interact with the page in place. Clicks, typing, navigation, new tabs, and tab closes become steps as you go.

Edit steps

Every step is a chip you can edit, reorder, or delete. Repick a target on the live page when the app changes. If/Else steps carry an editable predicate with THEN and ELSE branches. Each editing burst snapshots the test, and the History panel compares and restores versions.

Write steps in plain English

The plain-English composer parses a fixed grammar into the same step types the recorder produces. No model is involved, so a sentence either parses or the composer tells you which part it did not understand.

Author with AI

AI authoring needs a model configured for the workspace. Without one, the AI controls stay visible and return a disabled state instead of an error. The agent never writes selectors. Test Generation enumerates the interactive elements on the page, builds a locator ladder for each one, and the model returns only an element index and an action. The result is recorder-grade locators, whichever mode you use.

Generated code

The compiler is a pure function. The same test, environment, and options produce byte-identical TypeScript. It emits @playwright/test code you can read in a pull request. Export any test as a .spec.ts file from the test page. Generated code is TypeScript only.

Run and report

Batch runs compile a suite or an ad-hoc set of tests and run them with npx playwright test, with live per-test progress and a Playwright HTML report per run. Turn on TestDino reporting in project settings with a project API key. Each batch run then uploads its report to TestDino, and the run detail page links to the TestDino test run. Uploads never block the run. Learn how uploads work in Node.js CLI.

Locator health

When a primary locator fails on replay, the runner tries the next rung of the ladder and records the rescue on that step. Rescued steps show in Locator Health with the rung that resolved. Nothing changes in the test until you promote the working rung, so healing always has a person on the trigger.

Playwright skill

The Playwright skill documents the rules coding agents follow when they write Playwright by hand: role-based locators, web-first assertions, baseURL in config, traces on first retry, retries in CI. Test Generation applies the same rules through its compiler, so a spec you export reads like one an agent wrote with the skill loaded. Install the skill in your repo when an agent edits or extends exported specs, so the hand-written additions match the generated code.

Limits

  • Chromium only. Batch runs and recording do not use Firefox or WebKit.
  • TypeScript only. There is no JavaScript export.
  • Specs are downloaded or run in place. Test Generation does not commit to a repository or open pull requests.

Playwright Skill

Rules and guides for agents writing Playwright by hand

Node.js CLI

How batch run reports reach TestDino

Test Runs

Read the uploaded runs in TestDino

Flaky Test Detection

What TestDino does with retry-marked tests
Last modified on September 8, 2026