testsprite-onboard

Creates and smoke-runs a seed TestSprite test suite for repos with no existing tests.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/parthamehta123/loopcart-checkout-app --skill testsprite-onboard-parthamehta123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testsprite-onboard
Source: https://github.com/parthamehta123/loopcart-checkout-app/tree/main/.claude/skills/testsprite-onboard
Command: npx skills add https://github.com/parthamehta123/loopcart-checkout-app --skill testsprite-onboard-parthamehta123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New TestSprite projects start empty, and an empty project is the top reason users abandon the tool. This Skill takes a repository with zero tests and leaves it with a coherent, runnable test suite plus a few already-green smoke tests in a single pass. ## Core Features & Use Cases - Project provisioning: Creates a frontend project with a target URL and login credentials, or a backend project, and registers custom test-id attributes like data-element. - Two test-sourcing paths: Generates test proposals via testsprite test plan generate (with API spec upload for backend projects) and reviews them before accepting, or hand-authors frontend JSON plan files and backend Python test scripts when generation is unavailable. - Credit-conscious smoke runs: Runs only 2-3 high-value happy-path tests instead of the full suite, then reports test counts, results, dashboard links, and the cost of running the rest. - Use Case: After running testsprite setup on a fresh checkout app repo, invoke this Skill to create the project, seed 8-15 tests covering core flows like cart and checkout, and confirm a couple pass before handing off to continuous verification. ## Quick Start Set up a TestSprite test suite for this repository, which has no tests yet, and smoke-run a few of them.

Frequently Asked Questions about testsprite-onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up TestSprite tests for a new project?

Run testsprite setup first to configure an API key, then create a project with testsprite project create, passing a --url for frontend apps. Seed tests via test plan generate or hand-authored plan files, then smoke-run 2-3 tests with testsprite test run <testId> --wait.

How do I generate TestSprite tests automatically from my codebase?

Use testsprite test plan generate --project <projectId> after creating the project. Backend projects need an API spec uploaded first via testsprite project docs upload; frontend projects explore the live app directly. Review the staged proposals and accept the ones that fit.

Why does my TestSprite frontend test fail with no environment URL configured?

Frontend tests fail immediately when the project has no resolvable target URL. Always pass --url when creating the frontend project, and add --username/--password-file if the flows under test require login.

When should I not use the testsprite-onboard skill?

Do not use it when the project already has tests or when you only changed code and want it verified. Those cases belong to the testsprite-verify skill; onboarding is strictly first-run seeding for projects with 0-1 tests.

How do I handle authentication in TestSprite backend tests?

Configure a credential once on the project with testsprite project credential or auto-auth, then read the injected __AUTH_HEADERS__ variable in your Python test script. Never hardcode Bearer tokens or API keys, since they expire and cannot be rotated centrally.