See the Run Before You Spend a Credit On It.
A misconfigured CI job doesn't announce itself — it just runs the wrong tests against the wrong environment. --dry-run previews exactly which tests would run, which environment they'd target, and what actions they'd take, without executing a single step or spending a credit.
Built Into the Same CLI You Already Run
See Exactly What Would Run
--dry-run lists which tests a command would execute and in what order, without actually starting any of them.
Confirm the Right Environment
The preview shows which environment or base URL a run would target — so a config pointed at the wrong place gets caught before it touches anything.
Preview the Actions, Not Just a List
Dry run resolves what each test would actually do, step by step, instead of just naming the test IDs it would touch.
Spend Zero Credits
Nothing executes, so nothing is billed. Run --dry-run as many times as you need while you're wiring up a config.
$ testsprite test run --project my-project --dry-run
Dry run — no tests will be executed, no credits will be spent.
Environment: staging (https://staging.example.com)
Tests that would run (3):
- TC_checkout_flow (frontend, Playwright)
- TC_orders_api (backend, Python)
- TC_login_flow (frontend, Playwright)
Actions previewed: 14 steps across 3 tests
$ testsprite test run --project my-project --dry-run --output json
{"dryRun":true,"tests":3,"environment":"staging","credits":0}
Catch a Misconfigured CI Job Before It Runs for Real
A CI config that points at the wrong environment, or triggers the wrong test list, doesn't announce itself — it just runs the wrong thing. --dry-run lets you check the wiring before every commit spends a credit on a run you didn't mean to trigger.
Built for CI Pipelines You Want to Trust
A Global Flag
--dry-run works alongside commands that take action, like test run, so you can preview before committing to a real execution.
Safe to Run Anytime
Since nothing executes and no credits are spent, it's safe to drop into a pipeline step and run as often as you like while you're debugging a config.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Machine-Readable Output
Combine --dry-run with --output json to feed the preview into your own CI checks or scripts.
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
What does --dry-run actually do?
It previews exactly what a command would do — which tests would run, against which environment, and what actions they'd take — without executing anything or spending credits.
Does --dry-run work with any command, or just test run?
It's a global flag, so it works with commands that take action, letting you preview before committing to a real execution.
Does a dry run cost credits?
No — since nothing actually executes, a dry run doesn't spend credits. That's the point: you can check the wiring for free, as many times as you need.
How do I use this to sanity-check a CI config?
Add --dry-run to the same command your CI pipeline calls. If the environment, tests, or actions it previews don't match what you expect, fix the config before it runs for real.
Can I get the dry-run output in a machine-readable format?
Yes — pair --dry-run with --output json to get structured output you can parse in your own CI checks or scripts.