testsprite-onboard

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/nandini-teqfocus/poc-loop-engineering --skill testsprite-onboard-nandini-teqfocus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testsprite-onboard
Source: https://github.com/nandini-teqfocus/poc-loop-engineering/tree/main/.claude/skills/testsprite-onboard
Command: npx skills add https://github.com/nandini-teqfocus/poc-loop-engineering --skill testsprite-onboard-nandini-teqfocus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up an initial test suite for a new project is tedious, and an empty testing project leads to abandonment. This Skill bootstraps a complete, runnable TestSprite suite from your codebase in one pass, including a few already-green smoke tests. ## Core Features & Use Cases - Project Creation: Creates a TestSprite frontend project (with target URL and login credentials) or backend project via the TestSprite CLI. - Test Generation or Authoring: Generates test proposals from an uploaded OpenAPI spec and optional PRD, or hand-authors frontend JSON plan files and backend Python test files with concrete assertions. - Smoke-Run Validation: Runs 2-3 high-value happy-path tests to confirm a green verdict without consuming excessive credits. - Use Case: After running testsprite setup on a fresh repo, ask the agent to bootstrap tests — it reads your routes and flows, creates the project, seeds 8-15 tests covering core flows, and smoke-runs a few to confirm they pass. ## Quick Start Ask the agent to set up a TestSprite test suite for this repository using the testsprite-onboard skill.

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 repository?

Run testsprite setup first to configure your API key, then use this skill to create a project, derive tests from your codebase, batch-create them, and smoke-run a few. It produces a runnable suite in one pass.

How do I generate TestSprite tests from an OpenAPI spec?

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

When should I use testsprite-onboard vs testsprite-verify?

Use testsprite-onboard only when a project has zero or one tests, right after initial setup. Once a suite exists, switch to testsprite-verify, which runs tests covering code changes before reporting work done.

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

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

Can I hardcode API tokens in backend TestSprite tests?

No. Backend tests must read the injected __AUTH_HEADERS__ variable, which TestSprite populates from the project's configured credential. Hardcoded tokens expire quickly and trigger a warning during test creation.

What happens if test plan generation is not available?

The skill falls back to hand-authoring tests: JSON plan files for frontend flows and Python requests scripts for backend endpoints. This covers older CLIs, non-V3 accounts, or projects without a reachable URL.