Never Start a Test Plan From a Blank File.
Adding TestSprite to an existing codebase shouldn't mean writing your first test plan from nothing. testsprite test scaffold reads your project and generates a starter test-plan skeleton — with action and assertion steps already structured — so you're editing, not authoring from scratch.
Built Into the Same CLI You Already Run
Read From Your Codebase
testsprite test scaffold looks at the project you already have and drafts a starter test-plan skeleton from it — instead of handing you an empty file and a cursor.
Structured, Not Freeform
The output is a JSON test plan with action and assertion steps already laid out, so you're filling in and adjusting specifics rather than inventing the shape of the file.
Committed Like Any Source File
Because a test plan is just versionable JSON, the scaffolded file can be committed to git, diffed between edits, and reviewed in a pull request like the rest of your code.
A Starting Point, Not a Final Draft
Scaffold gets you to a working skeleton fast. From there, refine steps by hand, or run it through test lint before you execute it for real.
$ testsprite test scaffold Reading project structure... Drafting starter test plan... → wrote testplan.json (skeleton — action/assertion steps included) $ git diff testplan.json + edit steps, adjust assertions, commit like any source file
Adding TestSprite to a New Project Shouldn't Start With an Empty File
A blank test plan is a bigger obstacle than it looks — it's easier to edit a rough draft than to invent one. Scaffold gives you that rough draft, generated from the codebase you're already working in.
Built for Teams Adopting TestSprite Into an Existing Codebase
Works From What You Already Have
No need for a clean-slate project — test scaffold is meant for dropping TestSprite into a codebase that already exists.
Feeds the Rest of the CLI
Once scaffolded, the test plan is ready for the same commands as any other — test lint, test run, test diff, and the rest.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Setup
Run testsprite setup to connect your project, then test scaffold to get your first test plan instead of a blank one.
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 testsprite test scaffold actually generate?
A starter test-plan file — a JSON skeleton with action and assertion steps already structured, based on your existing codebase — so you have something to edit instead of a blank file.
Is the scaffolded test plan ready to run as-is?
Treat it as a draft. It gives you the shape and the steps to start from; you'll typically adjust specifics before running it for real against a live URL.
Can I edit the scaffolded file directly?
Yes — it's a plain JSON file. Open it, change or add steps, and it works with the rest of the CLI the same as a hand-written test plan would.
Can I commit the scaffolded test plan to git?
Yes. Because test plans are versionable JSON, the scaffolded file can be committed, diffed between edits, and reviewed in a pull request like any other source file.
When would I use scaffold instead of writing a test plan by hand?
Whenever you're adding TestSprite to a project that doesn't have a test plan yet — scaffold gives you a working starting point drawn from your codebase rather than starting from nothing.