testsprite-onboard

Creates and smoke-runs a seed TestSprite test suite for repositories without existing tests.

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

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 bootstraps a repo that has no tests yet into a coherent, runnable suite with a few already-green smoke tests in a single pass. ## Core Features & Use Cases - Project provisioning: Creates frontend projects with a target URL and login credentials, or backend projects, 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 request tests when generation is unavailable. - Credit-conscious smoke runs: Runs only 2-3 high-value happy-path tests instead of the full suite, then reports coverage, results, and the cost of running the rest. - Use Case: After running testsprite setup on a React SPA repo, invoke this Skill to create the project, generate tests covering auth, routine logging, and library browsing flows, and smoke-run two of them to a green verdict. ## Quick Start Set up a TestSprite test suite for this repository, which has no tests yet, and smoke-run a couple of the most important flows.

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, generate or author test plans, batch-create them, and smoke-run 2-3 happy-path tests. Frontend projects must include a target URL via --url.

How do I generate tests from an OpenAPI spec with TestSprite?

Upload the spec with testsprite project docs upload ./openapi.yaml --role api-doc, then run testsprite test plan generate. Review the staged proposals and accept the ones worth keeping with testsprite test plan accept.

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

Frontend projects require a resolvable target URL at creation time. Pass --url to testsprite project create, and add --username/--password-file if the flows under test require login.

When should I not use the TestSprite onboarding flow?

Skip onboarding when the project already has tests or when you only changed code and want it checked. Those cases belong to the testsprite-verify skill, which runs existing tests against changes.

How do I handle authentication in TestSprite backend tests?

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