Your Whole Suite. One Command.
Running tests one at a time doesn't scale past a handful. testsprite test create-batch <file> and test run --all --project <id> operate on your entire suite as a single operation — built for teams whose coverage has outgrown running things by hand.
Scales From 5 Tests to 500
Save What You Broke
testsprite test rerun --all --project <id> re-verifies every test in a project in one call — no scripting a loop yourself.
Understand What You Want
testsprite test create-batch <file> defines many tests from one file, so growing your suite is an edit, not hundreds of individual commands.
Validate What You Have
testsprite test run --all --project <id> --wait --output json runs the entire suite and waits for one consolidated result.
Suggest What You Need
Failures in a batch run still get individual failure bundles — scale doesn't cost you the detail on any one test.
$ testsprite test create-batch tests.json ✓ 84 tests created in prj_8f2a $ testsprite test run --all --project prj_8f2a --wait --output json ✓ 81 passed ✗ 3 failed (84 total) $ testsprite test rerun --all --project prj_8f2a --wait --output json ✓ 84 passed (3 fixed since last run)
Coverage That Scales With Your Suite, Not Your Patience
Whether it's 20 tests or 2,000, run --all and rerun --all are the same command — the CLI doesn't get slower to operate as your suite grows, even if the run itself does.
Built for Suites That Have Outgrown Manual Runs
Batch Create
test create-batch and test update manage many tests from a file instead of one command per test.
Batch Cleanup
testsprite test delete-batch <file> removes a whole set of retired tests in one call.
Free Community Version
Offers a free community version, making us accessible to everyone.
Same Failure Detail at Scale
Every test in a batch still gets its own failure bundle if it fails — nothing gets summarized away.
Trusted By Businesses Worldwide
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
How many tests can I run in one batch?
As many as your project has — run --all and rerun --all operate on the entire project's test set in one call, whether that's a dozen tests or a few hundred.
Do I lose detail on individual failures when running in batch?
No — each test in the batch still gets its own failure bundle if it fails. Batch operations save you commands, not visibility.
How do I add a large number of tests at once?
testsprite test create-batch <file> takes a file defining many tests and creates them all in one call.
How do I remove a large number of tests at once?
testsprite test delete-batch <file> removes a defined set in one call — useful when retiring an old suite.
Can I combine batch runs with CI?
Yes — test run --all is exactly the kind of command that fits as a single CI step, authenticated non-interactively with TESTSPRITE_API_KEY.