English in, tests out
You already know how to specify a test — you do it every time you explain a bug to a teammate. That explanation is the test.
- Plain English. "Log in as an approver, reject the pending expense, and check the requester sees the rejection reason." That is a complete test.
- Or just say it. Dictate by voice while you click through the flow yourself. Walking the app and describing it out loud is the fastest spec format ever invented.
Drafting is a conversation, not a commit
A drafted test is not gospel. You watch it run before you rely on it.
Speak or type the intent
One or two sentences. The agent fills in the mechanics — where to click, what to read — from what it has learned about your app.
Watch the draft run
The first run happens in front of you, step by step, in a real browser. You see exactly what the agent understood — and exactly where it guessed.
Keep what's right
Correct a step in plain English, tighten an assertion, drop what you don't need. What survives is a test you actually trust, because you saw it work.
Your tests are portable YAML — you own them
Every test compiles to a flat, human-readable YAML file. No proprietary binary, no encrypted project format, no export tax. A test reads like this:
name: Invited teammate appears as pending
steps: open Members → send invite → verify pending row
That file is the source of truth. Check it into your repo, review it in a pull request, edit it in any text editor — a product manager can read it and a new hire can understand it in one sitting. If you ever leave TestAutomate, your tests leave with you as documents any human or agent can follow.
Because tests describe intent instead of selectors, they survive redesigns. A renamed button or a reshuffled layout is a non-event: the agent re-finds the flow, and if the UI changed in a way that still works, you get an advisory flag — not a broken suite.
Do I need to know how to code?
No. If you can describe a flow to a colleague, you can author a test. Developers who want to read or edit the YAML directly can — it is plain text — but nothing requires it.
What happens when the UI changes?
The agent navigates by understanding the page, not by stored selectors. Cosmetic changes get an advisory flag if worth noting; the test keeps running. Only a genuinely broken flow fails.
Can I edit a test after it's drafted?
Yes — in plain English ("also check the confirmation email banner appears") or directly in the YAML. Either way the change is visible, reviewable text.
Your next test is one sentence away
Type it or say it. Watch it run. Keep it forever as YAML you own.