01
Plain-English tests
Write the workflow as readable lines of intent, with saved values and reusable actions when you need them.
Natural-language browser testing
Write the workflow.Watch the browser prove it.
TestPilot turns plain-English steps into real browser actions, visible checks, and review-ready evidence—locally or across CI.
Natural languageReadable intent
Computer useVisible interaction
Real evidenceEvery step captured
01 Flight plan
1new test named "Checkout keeps its promise"
2login with test credentials
3open the product catalog
4add the first available item to the cart
5verify the cart total matches the item price
6submit the order
7verify confirmation is visible
shop.example.test/catalog
NORTH / SUPPLY
Cart 1
Field Pack / 01
Designed for the miles ahead.
$84.00In stock
Reading visible UI
Run 8F2CExecuting in a real browser
✓Open the product catalog2.1s
✓Add the first available item3.2s
✓Verify the cart total4.3s
Submit the orderrunning
PLAIN ENGLISH✦COMPUTER USE✦REAL BROWSERS✦STEP SCREENSHOTS✦HTML + JUNIT✦CI SHARDING✦PLAIN ENGLISH✦COMPUTER USE✦REAL BROWSERS✦STEP SCREENSHOTS✦HTML + JUNIT✦CI SHARDING✦
A better testing language
Testing should read like intent—not plumbing.
The person who understands the workflow should be able to read the test. TestPilot keeps the scenario human, then uses computer use to work through the visible browser.
“
Create a uniquely named record, try to create it again, verify the duplicate warning appears, then clean up.
WHAT STAYS HUMANIntent, outcomes, and business meaning.
WHAT TESTPILOT FLIESNavigation, interaction, checks, and evidence.
From words to proofOne clear flight plan.
One clear flight plan.
Three simple phases.
Start with the behavior that matters. TestPilot handles the browser journey and leaves a trail your team can review.
Write the intent
Readable by everyone. Precise enough to fly.
Describe the workflow as a sequence of outcomes. Reuse guided actions for the parts your team performs every day.
new test named "Order total stays consistent" open the product catalog add a random available item to the cart save its displayed price as "item price" open the cart verify the total equals "item price"
Reusable action matched · open the product catalog
The flight deck
Everything needed to move from scenario to signal.
02
Real browser control
AI reads the visible interface, then navigates, clicks, types, and verifies the same experience your users have.
03
Evidence by step
Follow every running, passed, or failed step and keep the screenshot that explains what happened.
04
Built for CI
Run one browser per container, balance the suite across shards, and merge the results into one review-ready report.
One test. Fully visible.
The entire run, without the black box.
Keep the instructions, the browser, and the evidence in one view— so the team can follow what the AI is doing as it happens.
One run. One report.
When a test speaks, it brings receipts.
Every shard contributes to one clean result: a browsable HTML run, machine-readable output, and screenshots that stay attached to the exact step that produced them.
- ✓ Pass or failure status for every step
- ✓ Screenshots for fast visual triage
- ✓ HTML, JSON, and JUnit results
- ✓ Combined evidence from parallel CI shards
CHECKOUT KEEPS ITS PROMISE
42.8s6 of 6 steps passed
✓ passed6. verify confirmation is visible4.2s
Confidence by design
Give the AI a clear runway.
Keep browser runs inside the environments you approve, separate checks from mutations, and stop stuck steps before they hold up the rest of the suite.
01Approved HTTPS environments
02Protected credential handling
03Read-only and mutation intent
04Hard deadlines for stuck steps
Ready when you are
What should the browser prove next?
Tell us about the workflow you want to make simpler, more visible, and easier to trust.
Start a conversation