Your Test Plan Is a JSON File. Treat It Like One.
Every TestSprite test plan is a plain JSON file made of action and assertion steps. Pull it with testsprite test code get, commit it, diff it in a pull request, and let a teammate review it — instead of leaving it trapped inside a proprietary GUI recorder.
Built Into the Same CLI You Already Run
Plain JSON, Not a Black Box
Each test plan is a readable JSON file made of explicit action and assertion steps — you can open it, grep it, and understand exactly what it does without replaying a recording.
Commit It Like Any Other File
Because a test plan is a file on disk, it lives in your repository next to the code it tests — tracked, branched, and versioned the same way.
Diff It in a Pull Request
Changing a test plan produces a real git diff — a reviewer sees exactly which step changed, instead of having to trust that a re-recorded flow still does the same thing.
Edit It Directly
Pull the underlying file with testsprite test code get, change the steps by hand in your editor, and push it back with testsprite test code put.
$ testsprite test code get TC_checkout_promo
Wrote test-plans/TC_checkout_promo.json
$ git diff test-plans/TC_checkout_promo.json
{
"action": "click #promo-code-input",
- "assertion": "input is focused"
+ "action": "type '10PERCENT' into #promo-code-input",
+ "assertion": "discount line shows -10%"
}
$ testsprite test code put TC_checkout_promo
Updated test plan from local file
Stop Reviewing Test Coverage by Screen-Recording
A recorded flow lives inside a proprietary tool, so a teammate has to trust it or re-run it to know what changed. A JSON test plan can go in the same pull request as the code it tests and get reviewed the same way.
Built for Teams That Already Review Code
Fits Your Existing Workflow
A test plan sits in the same repository and the same pull request as the change it covers — reviewed with the git diff habits your team already has.
Scaffold, Then Refine
testsprite test scaffold generates a starting test plan; testsprite test lint validates its structure before you commit.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Run Diffing
Once a test plan is versioned, use testsprite test diff to compare two runs against it and see exactly what changed in behavior.
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 it mean that a test plan is "just JSON"?
Each test plan is a plain JSON file made of action and assertion steps — no proprietary format and no binary recording, so it opens in any editor and diffs cleanly in git.
How do I get the underlying file for a test plan?
testsprite test code get <testId> pulls the JSON to your local machine. Edit the steps directly, then push your changes back with testsprite test code put.
Can a teammate review a test plan the way they review code?
Yes — because it's a diffable JSON file, it can go into the same pull request as the change it tests and be reviewed with an ordinary git diff, not a screen recording.
Do I have to build every test plan from scratch?
No — testsprite test scaffold generates a starting structure, and testsprite test lint validates it before you commit.
What if I want to compare two test runs, not two file versions?
That's testsprite test diff — it compares two runs to show what changed in execution, separate from the test plan's own history in git.