skills.rest
nandini-teqfocus
nandini-teqfocusCOMMUNITY
Explore all skills by this author →
GitHub

testsprite-verify

Runs TestSprite CLI tests against shipped code changes and reports terminal verdicts.

Updated Sep 11, 2026
Search Tags:#test automation#cli#verification#frontend testing#backend testing#ci#testsprite
One-click install
npx skills add https://github.com/nandini-teqfocus/poc-loop-engineering --skill testsprite-verify-nandini-teqfocus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testsprite-verify
Source: https://github.com/nandini-teqfocus/poc-loop-engineering/tree/main/.claude/skills/testsprite-verify
Command: npx skills add https://github.com/nandini-teqfocus/poc-loop-engineering --skill testsprite-verify-nandini-teqfocus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a feature or fix, spec review and unit tests alone cannot confirm the change works for a real user. This Skill closes that gap by running the relevant TestSprite tests through the testsprite CLI against the actual change and inspecting failure artifacts before the work is reported as done. ## Core Features & Use Cases - One-test minimum enforcement: Every shipped feature gets at least one TestSprite run to a terminal verdict (passed, failed, blocked, or inconclusive) before being called done. - Flexible test sourcing: Run an existing test that covers the change, create a new frontend plan or backend Python assertion test, or batch a frontend coverage set of 2-5 plans. - Deployed and local targets: Test a deployed URL via --target-url, or tunnel a local frontend server with --local <port> when no deployment exists. - Failure triage: Distinguish plan-quality problems from real product bugs by reading step traces, and download failure artifacts (video, root-cause hypothesis) before reporting. - Use Case: You just changed the checkout form in a TestSprite-linked repo. The Skill finds the project, drafts a frontend plan asserting the updated total, runs it against the PR preview URL, and reports the verdict with a dashboard link. ## Quick Start Verify my just-finished change by running the relevant TestSprite test through the testsprite CLI and tell me the verdict.

Frequently Asked Questions about testsprite-verify

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

FAQPage Schema
How do I verify a code change with TestSprite before marking it done?▼

Run at least one TestSprite test to a terminal verdict using the testsprite CLI: either `testsprite test run <id> --wait` on an existing test, or `testsprite test create --plan-from plan.json --run --wait` for a new frontend plan. Unit tests and lint do not count as verification.

How do I run TestSprite tests against a local development server?▼

Use `testsprite test run <test-id> --local <port>` to tunnel your machine's loopback address to the test runner. This works for frontend tests only and requires an API key with the run:tunnel scope; backend tests must target a deployed URL.

Can TestSprite backend tests import my project's source code?▼

No. Backend tests run in a locked-down sandbox with only the Python standard library plus requests, pytest, numpy, and scipy. Test the API over HTTP with requests against the target URL instead of importing application modules.

Why did my TestSprite backend test pass without running its assertions?▼

The runner executes the file top-to-bottom and does not auto-discover test functions like pytest does. A test function that is only defined but never called silently passes, so end the file by explicitly invoking your test functions.

When should I skip running TestSprite verification?▼

Skip only for docs-only edits, pure build or config changes with no behavior impact, or when the repo is not wired to TestSprite at all. If you cannot run a test due to missing credentials or target URL, state that explicitly instead of claiming done.

How do I handle authentication tokens in TestSprite backend tests?▼

Never hardcode credentials in test code. Configure the credential once on the project with `testsprite project credential`, then spread the injected `__AUTH_HEADERS__` dict into every authenticated request so the managed block stays fresh across runs.

Related Skills

Explore More Software Engineering Skills→
TEC037TEC037

testsprite-verify

Runs TestSprite CLI tests against shipped code changes and reports terminal verdicts.

Community
Advanced
openchamberopenchamber
9.5k

pr-review

Review GitHub pull requests and produce a maintainer-ready verdict with an actionable artifact.

Official
Advanced
olimpus-softolimpus-soft

review-frontend

Automate frontend code reviews for security, performance, and accessibility issues.

Official
Advanced
Euraika-LabsEuraika-Labs
14

bug-report

Generate structured bug reports with reproduction steps, severity, and context.

Official
Advanced