Questions, answered plainly.
What TestPilot needs, what it checks, how it behaves on a live site, where your data goes, and how to read its results. If something isn't here, ask us when you book a demo.
The basics
What is TestPilot?
TestPilot is an automated end-to-end testing tool for websites. You give it your site’s address; it explores the site, writes focused tests with Claude, runs them in a real Chromium browser, and reports what’s broken.
What do I need to run TestPilot?
A machine you control, Node.js, and Claude Code signed in on that machine; an SMTP account only for emailed reports.
Do I have to write tests or code?
No. Auto-Test crawls the site and writes the tests for you. You can also describe a test in plain English or record one by clicking through the site, but you don’t have to.
Which AI does TestPilot use?
Claude, through the Claude Code command-line tool on the machine that runs TestPilot, signed in with that machine’s Claude account. Rule-based checks always come first.
How do I get an account?
Sign up with your email and a password; we email you a 4-digit code to confirm it. Each account sees only its own websites, tests and reports.
Can several people on a team use one TestPilot?
Each person signs up with their own email and has their own websites.
How much does it cost?
One website is free. Basic is ₹1,499 a month for 3 websites, and Pro is ₹4,999 a month for 10; paying for a year gets two months free. Payments aren’t online yet: tell us which plan and we set it up.
What gets tested
What does Auto-Test actually check?
That pages load, links answer, menus navigate, forms submit, and search, filters, sorting, AI assistants and widgets work. One test per feature, kept simple.
Will it work on my WordPress, Webflow, Wix or React site?
It’s built for any website. It reads page structure (headings, landmarks, roles, labels, input types) rather than relying on a specific builder, follows single-page-app route changes, and handles cookie banners, lazy loading, iframes and open shadow DOM. Web tests run in Chromium.
Can it test file uploads?
Yes. TestPilot creates a real, readable file that matches what the field accepts, or you supply your own in the Data tab.
Does it check accessibility and performance?
Every web test runs an axe accessibility scan. Lighthouse scores (performance, accessibility, best practices, SEO) can be turned on per run or run as a separate audit.
Can it test mobile apps?
Experimentally: iOS apps on a simulator (via Appium), Android apps on an emulator or device, and Flutter apps using a vision-based driver. It needs a local emulator or simulator.
Can I get my tests out again?
Yes. Tests, their steps and their version history live in a SQLite database file (data/testpilot.db) on your own machine, which any SQLite tool can read.
How long does a run take?
It depends on the site and on how fast the AI answers. One example from our own instance: a run of 36 tests took 201.6 seconds (5.8 s per test) on 30 September 2026. We can show timings on your own site in the demo.
Safety on your live site
Will the tests submit real data to my forms?
Forms are submitted for real, with test data your team can spot: an example.com email, an obvious test phone number and a “please ignore” message.
How many submissions will my forms get?
One per tested form per run, so a daily schedule means one entry per form per day. TestPilot doesn’t delete them, and they’re easy to filter.
Will it place orders, book slots or open support tickets?
It can. Auto-Test submits the forms it finds and doesn’t skip order, booking or support forms on its own, and a phone field can trigger whatever your site does with a number. To keep a form out, schedule only the tests you choose (select them, then Schedule) or delete that form’s test. Every submission is labelled as above, so your team can recognise it.
Will it change my account or log me out?
Auto-Test won’t: it never tests sign-in, profile or settings pages and never clicks Log out. A dedicated test account is still the safest choice.
Does TestPilot get around CAPTCHAs?
No, never. A CAPTCHA or bot block is reported as Blocked, which doesn’t lower your health score.
Security and data
Where does my data go?
Results stay on the machine running TestPilot. What the AI needs goes to Anthropic through Claude Code.
Where are my login passwords and 2FA secrets kept?
In the local database on the machine running TestPilot, not encrypted at rest today. The app never sends them back out.
Does TestPilot send anything to you?
No. Nothing goes to the TestPilot team.
Results and reports
What happens when my site changes and a button moves?
TestPilot finds the element again and saves the fix with version history, but refuses to guess where a guess could cause a false pass.
How do I know a failure is a real bug and not a broken test?
Every result is classified, and only “site bug” counts against your site’s health.
What do I do about “Needs test maintenance”?
Click Regenerate on the test: TestPilot opens its page, tries it for real and rewrites it from what actually happens. A test of something the page doesn’t do is replaced by one that works, and the new test runs once before it’s saved. Or edit the step it names. The old version stays in its history. Tests saved as “Needs review” are switched off and don’t run; regenerate, edit or delete them, or switch one back on from Edit. None of these lower your site’s health.
What if my site is down when a scheduled run starts?
TestPilot checks the site twice, 30 seconds apart, before running anything. If it’s down, the run stops and you get one short “Site down” email.
Can it run tests automatically every day?
Yes, as long as the machine running it is on: once, daily, weekly or every N minutes, with the report emailed as a PDF.
What’s in the report?
Real site issues first, then warnings, blocked tests, tests needing maintenance and passes, with a screenshot for every step.
What is a warning?
A feature that works but isn’t what it says, like a “Privacy” link that opens the Contact page. It doesn’t count as a failure.
Still have a question?
Book a demo and ask it on a call, with TestPilot running in front of you.