Integration: Playwright export
Export plain-English tests to Playwright
Available
Specs can be exported to Playwright tests in TypeScript. A team can keep plain-English specs as the source and still own Playwright code.
Export is the exit path: the tests do not stay locked in the spec format.
Teams that already run Playwright can keep existing code tests and add plain-English specs next to them for flows owned by people who do not write code.
Healing and triage apply to runs through the platform. An exported Playwright test is plain code and follows Playwright's own locator and retry behaviour.
What Playwright documents
- Locators are the central piece of Playwright's auto-waiting and retry-ability. [Microsoft (Playwright)]
- Playwright can run tests on Chromium, WebKit and Firefox browsers as well as branded browsers such as Google Chrome and Microsoft Edge. [Microsoft (Playwright)]
Questions
Is this an AI layer for Playwright tests?
It works the other way round: tests are written as plain-English specs and can be exported to Playwright. Existing Playwright code is not converted into specs.
Which language does the export use?
TypeScript.
Do exported tests heal?
No. Healing happens in runs through the platform. Exported code uses Playwright's own locators.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.