Stop Scraping Terminal Output for Test Results.
Every testsprite command accepts --output json, swapping the human-readable terminal report for structured, parseable output — so your dashboard, Slack bot, or CI script gets clean data instead of a wall of text to regex apart.
Built Into the Same CLI You Already Run
--output json turns every command into data you can actually trust.One Flag, Every Command
--output json is a global flag — run it with test run, test get, test list, or almost any other command and get the same structured shape back instead of a different text format each time.
Built for Pipelines, Not Eyeballs
Structured output means a CI script can check a field and decide what happens next programmatically, instead of grepping for a phrase that might change between CLI versions.
Feed Your Own Dashboard
Pipe --output json results into whatever you already use to track builds — a Slack bot, an internal dashboard, an incident tool — without maintaining a text scraper.
Preview Before You Commit
Pair --output json with --dry-run to see exactly what a command would return before it actually executes.
$ testsprite test get TC_checkout_promo ...formatted, human-readable report printed to the terminal... $ testsprite test get TC_checkout_promo --output json ...the same result, returned as structured JSON on stdout... → pipe it straight into a script, a dashboard, or a Slack bot
Don't Build a Text Scraper When JSON Already Exists
Teams that need CI to react to results usually end up writing regex against colored terminal text — brittle, and it breaks the moment the CLI's formatting changes. --output json gives you the same data as a stable, parseable structure instead.
Built for Scripts, Not Just Terminals
Works Across the CLI
--output json is available on most testsprite commands, so you don't need a different integration approach for each one.
Drop Into Any CI Script
Structured output is easy to parse from GitHub Actions, GitLab CI, or any pipeline step, so you can gate a build on the actual result instead of a string match.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Non-Interactive Setup
Combine --output json with testsprite setup --from-env --yes --agent <name> for a CI job that installs, configures, and reports back without a human in the loop.
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 --output json actually change?
It switches a command's output from human-readable terminal text to structured, parseable output on stdout — the underlying result is the same, just in a format your own tools can read.
Which commands support --output json?
It's a global flag available on most testsprite commands, not a special mode built into just one of them.
Can I use this to feed a Slack bot or an internal dashboard?
Yes — since the output is structured, any script that can parse it can forward the result wherever your team already looks for build status.
Does --output json work with --dry-run?
Yes — combine them to see exactly what a command would return before it actually executes, useful when you're building a new integration.
Do I only get this in CI, or also locally?
Same flag either way — it works the same whether you're running testsprite locally, in GitHub Actions, GitLab CI, or your own agent loop.