testsprite-ai-testing-cli

Create, run, and verify frontend and backend tests via the TestSprite CLI.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill testsprite-ai-testing-cli-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testsprite-ai-testing-cli
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/testsprite-ai-testing-cli
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill testsprite-ai-testing-cli-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @testsprite/testsprite-cli.

What problem does it solve? Manually writing and maintaining end-to-end tests is slow, and coding agents lack a structured way to verify that the code they produce actually works against a live application. This Skill drives the TestSprite CLI to create, run, and verify real browser and API tests, closing the loop between code changes and verified behavior. ## Core Features & Use Cases - Test Creation & Execution: Create frontend (Playwright-based) and backend API tests from plan files, run them in the cloud, and wait for structured JSON results with clear exit codes. - Failure Diagnosis Loop: Download self-contained failure bundles (failure.json, screenshots, DOM snapshots, test source) with root-cause hypotheses, then rerun after fixes. - CI & Agent Integration: Non-interactive authentication, dependency-aware backend test waves, batch operations, and JSON output for scripting in CI pipelines. - Use Case: An agent implements a new checkout feature, creates a frontend test from a plan JSON, runs it, receives a failure bundle showing a changed button selector, fixes the code, and reruns until the test passes. ## Quick Start Install the TestSprite CLI with npm, run testsprite init with your API key, then ask the agent to create and run a frontend test for your checkout flow and report any failures.

Frequently Asked Questions about testsprite-ai-testing-cli

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

FAQPage Schema
How do I run automated tests with the TestSprite CLI?▼

Install the CLI with npm install -g @testsprite/testsprite-cli, authenticate via testsprite init, then create a test with testsprite test create using a plan file and the --run --wait flags. Exit code 0 means pass, 1 means fail, and 2 means an error occurred.

How do I get test failure details from TestSprite?▼

Run testsprite test failure get with the test ID and an --out directory. It downloads a failure bundle containing failure.json with the failing step and root-cause hypothesis, plus screenshots, DOM snapshots, and the generated test source.

Can I integrate TestSprite into a CI pipeline?▼

Yes. Set TESTSPRITE_API_KEY as an environment variable, run testsprite init --from-env --yes for non-interactive setup, then use testsprite test rerun --all --wait --output json and parse results with jq to fail the build on test failures.

Does TestSprite support backend API tests with dependencies?▼

Yes. Backend tests declare --produces and --needs flags to express data dependencies between tests. When rerunning all tests in a project, TestSprite executes them in dependency wave order so prerequisite data exists.

Why is my TestSprite test stuck in running status?▼

A stuck run usually means a step is still executing or hung. Check progress with testsprite test result and testsprite test steps to see the current step, and cancel the run from the web dashboard if it does not complete.