Tests in plain English
Tests written in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
A test is a YAML file with a name, a start URL and a list of steps. Each step is a sentence such as Click "Checkout". At run time the platform finds the element or action the sentence describes on the live page and performs it. Assertions are written the same way, after assert:.
1name: Checkout with a saved card2url: https://app.example.com3tags: [checkout, smoke]4env:5 EMAIL: ${TEST_EMAIL}6 PASSWORD: ${TEST_PASSWORD}7steps:8 - Log in with EMAIL and PASSWORD9 - Open the cart10 - Click "Checkout"11 - Choose the saved card ending in 424212 - Click "Place order"13 - assert: The order confirmation page shows an order number14 - api:15 get: /api/orders/latest16 expect:17 status: 20018 body.status: confirmedWhat it does not do
Does not accept free-form prose without step structure; does not generate assertions that were not written.
When it applies
- The people who know the flow (QA, product, support) are not the people who write test code.
- A suite written in code breaks after most UI changes because it depends on selectors.
- Coding agents write features faster than engineers can write tests for them.
- An agency hands the test suite to a client who has to read and own it.
Related integrations
Questions
What is natural language test automation?
Tests are written as sentences describing what a user does and what should be true, instead of code that drives the browser. In AI Testing Platform the sentences are steps in a YAML file, and the platform resolves each one against the live page when the test runs.
How is a plain-English spec different from Gherkin (BDD)?
Gherkin steps need step definitions written in code that connect each sentence to the browser. A plain-English spec has no step definitions: the platform resolves the sentence against the page at run time.
Can I write free-form prose instead of steps?
No. A spec needs step structure: a list of steps, one action or assertion per step. Free-form prose without that structure is not accepted.
Does the platform invent assertions?
No. It checks only the assert: lines that were written. A test without assertions passes when every action completes.
Can I keep using Playwright?
Yes. Tests can be exported to Playwright in TypeScript, so a team is not locked into the spec format.
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.