Quickstart
Your first test and its result in about five minutes. No card needed.
1. Write what should happen#
Go to testsy.dev and write the test in the box at the top: what the tester should do, and what must be true for it to pass. Name the page it starts at, for example:
Order a linen shirt on https://shop.example.com and check the cart total matches the product price.Choose Website, iOS app or Android app. You can attach files the tester needs, such as a CSV to import. Then press Run this test free.
2. Review the plan#
The assistant drafts the plan straight away, before you sign up: numbered steps, the checks that must be true to pass, and any questions only you can answer (for example which account to sign in with). Ask for changes in the chat ("also check the price on the cart page") or edit the plan directly. Before you sign up, each test has 8 revisions with the assistant; your test is kept in your browser, so a refresh does not lose it.

3. Save and run#
Press Save and run (or Save). Create your account with an email and password, or continue with Google, and confirm your email address: we send a link that works for 3 days. Your test is saved in a project named after the site, and the run starts.
You can also start in the app: sign up at app.testsy.dev, then New test.
4. Watch it run#
The run page shows the tester's screen live, the checks as they are verified, and what the tester is doing. A run usually takes 2 to 8 minutes. You can leave the page: the result is kept, and you can ask to be emailed when it finishes.
5. Read the result#
The result says whether the test passed, failed, was blocked by the site or is inconclusive, with the value behind every check and where on the screen it was read. A failure comes with the expected and seen values, the steps to reproduce and a fix prompt for your coding agent. See Proof, replay and video.

The free trial#
The free trial includes 10 runs, once, for websites and for Android and iOS apps, one run at a time, in one project of up to 20 tests. Runs blocked by the site, runs that fail on our side and runs you stop are not counted. See Plans and billing.
Next: run your tests after every deploy, or let your coding agent write and run them.