Tests learned from your docs, repo and running app
An agent that shows up already briefed. Point TestAutomate at your docs and help center. It turns them into retrievable playbooks — then gets smarter with every run, and remembers what it learns for your whole team.
From help center to skills, in plain words
A generic browser agent opens your app cold and has to guess where everything lives. Yours doesn't have to. Ingestion works in four steps:
Crawl
Give it the URL of your docs or help center. It walks the pages the way a careful reader would — articles, guides, FAQ entries.
Extract
It pulls out the task-shaped knowledge — "to create an invoice, open Billing and click New" — and discards navigation chrome, marketing copy, and boilerplate.
Classify
Extracted knowledge is organized into named skills: "Create an invoice." "Invite a teammate." "Change a plan." Each skill is a small, reusable playbook.
Retrieve
At run time, the agent pulls only the skills relevant to the test at hand. It never stuffs your whole manual into context — that keeps runs focused and cheap.
Knowledge you can trust
Docs go stale. A skill scraped from a help article written two redesigns ago should not be trusted like one confirmed by yesterday's run — so what the agent sees in a real run wins.
- Correction. When the live app contradicts the docs, the run's observation is what gets remembered.
It gets smarter with every run — for everyone
Skills from your docs are the starting point. The rest is learned on the job, and what one run learns, every later run in your org inherits.
Login recipes
The first run figures out your staging login — the redirect, the test account, the MFA quirk. Every run after that skips the rediscovery and goes straight to work. Recipes work with your real logged-in Chrome, including behind VPN and SSO.
Nav notes
"Settings is under the avatar menu." "The export lives on the reports page, not the dashboard." Small facts that would cost a cold agent a dozen wandering steps are remembered once and reused forever.
Quirks
Every app has them: the modal you must close before the save button responds, the table that loads on scroll. Quirks get written down the first time they bite — and your teammate's run tomorrow never trips on them.
Feed it your help center this afternoon
Ingestion runs on your docs as they are — no restructuring, no annotations, no test IDs.