Moving from TesterArmy to Testsy before 15 January
TesterArmy's dashboard closes after 15 January 2027. Here is what carries over to Testsy, what does not, and how to move a plain-English test suite.

What is happening to TesterArmy#
TesterArmy is winding down. Its site says sign-ups are closed, existing accounts keep working until 15 January 2027, the dashboard closes after that date and nothing is billed afterwards. Tests are not moved anywhere automatically. A data export is promised, and was not available yet when we checked on 20 November 2026 (tester.army).
The team points its customers to e2e, their open-source testing framework. With e2e a test becomes a TypeScript file that you run on your own machine or in your own CI (e2e migration guide, read on 20 November 2026).
So the first decision is not which product. It is where you want your tests to live.
Choose by where the tests should live#
| You want | A good fit |
|---|---|
| Tests as code in your repository, run with your own model key on browsers and phones you provide | e2e |
| To keep describing a test in plain English and have someone else run the browsers and phones | Testsy |
If the first row is you, use e2e. Its migration guide has a coding agent read your saved TesterArmy tests and rewrite them, which is less work than anything we can offer for that route.
The rest of this post is for the second row: teams who chose a hosted tester because they did not want test code, or because the people writing the tests are not developers.
What carries over#
Testsy works the way you are used to: you describe what to do and what must be true at the end, and the test runs in Chrome or on iPhone, iPad and Android on our side.

| In your TesterArmy test | In Testsy |
|---|---|
| Steps written in plain English | Steps, in the same words. Paste them into New test; the assistant drafts a plan and nothing runs until you confirm it. See Write a test. |
| An assertion with an expected result | A check. Every result shows the value the check was decided on and where on the screen it was read. See Proof, replay and video. |
| A login step with a saved account | A sign-in account, stored encrypted. The tester types the password into the form; it never reaches the AI. See Sign-in accounts. |
| A temporary inbox for sign-up emails | A mailbox for the run, on every plan including the free trial. See Mailbox, phone number and endpoints. |
| A group of tests | A project. Run one test or the whole project. |
| A browser region | Browse from a country, chosen once for the workspace. See Network and allow-listing. |
| Android and iOS app tests | Upload the build and write the test the same way. See Android and iOS apps. |
Testsy also runs saved tests on a schedule, from GitHub Actions and GitLab CI, and from a coding agent over MCP.
What does not carry over#
Better to know before you start:
- There is no importer. You paste each test's steps. TesterArmy's export was not available when we wrote this, so there was no format to read.
- No microphone step. If a test speaks into the app, it cannot move yet.
- No accessibility audit. Testsy checks what you ask it to check; it does not run an audit beside the test.
- No photo-library files on phones. Test files are picked in a website's file chooser. There is no step that loads your own pictures into a phone's photo library.
- The country is per workspace, not per test. A suite that tests several regions needs a workspace for each, or one region at a time.
If one of these is the centre of your suite, e2e or another hosted tool will serve you better, and you will find that out faster from this list than from a trial.
Move the suite#
- Copy your tests out while the dashboard works. For each test, keep the steps, the expected results and which account it signs in with. Do not wait for the export.
- Create a workspace. The free trial has 10 runs and room for 20 saved tests in one project, which is enough to move a small suite and see real results before paying.
- Add the sign-in accounts first. A pasted test that names an account the project does not have is flagged in the plan, so storing them first saves a round trip.
- Paste one test and read its plan. Check that each expected result became a check you could judge by looking at the screen. "The order is saved" is weak; "the order list shows order 1042 with status Paid" is a check.
- Run it and open the result. Compare what each check was decided on with what you expected. A run usually takes 2 to 8 minutes.
- Move the rest, then add schedules or CI. Tests that passed in TesterArmy and fail here deserve a look at the replay before you change them: sometimes the old test was passing on less evidence.

What a result looks like#

Two real runs against our own practice site are public, with no account needed: one that passed and one that failed. The failed one is worth a minute. The page said the export had started and the file was named report.csv, but the file contained an HTML error page, and the run failed on that.
What it costs#
A run is one test, run once, on one platform, however long it takes. An app run counts the same as a web run. Runs that a site blocks, runs that fail on our side and runs you stop are not counted.
| Free trial | Starter | Team | Growth | |
|---|---|---|---|---|
| Price | Free | $49 a month | $149 a month | $299 a month |
| Runs included | 10, once | 100 a month | 500 a month | 1,200 a month |
| Extra runs (packs of 50) | — | $30 | $20 | $15 |
| Web runs at a time | 1 | 5 | 10 | 20 |
| App runs at a time | 1 | 1 | 3 | 10 |
| Android and iOS app tests | Yes | Yes | Yes | Yes |
| Members | 1 | 5 | 25 | 100 |
| Projects | 1 | 2 | 5 | 15 |
| Tests | 20 | 300 | 1,000 | 5,000 |
| Assistant drafts a day | 40 | 300 | 300 | 300 |
| Phone number and endpoint calls | — | Yes | Yes | Yes |
| Invite people | — | Yes | Yes | Yes |
Moving a large suite, or not sure a test will carry over? Write to contact@testsy.dev with one example and we will tell you plainly whether it fits.
Filed underChoosing a tool