speckit-runtests

Executes shell-scripted integration tests for the active feature spec and reports pass/fail results.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-runtests-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-runtests
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/speckit-runtests
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill speckit-runtests-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running integration test scripts for a feature spec manually requires locating the right directory, checking environment prerequisites, executing the correct scripts, and interpreting raw output. This Skill automates that entire flow and presents a clean pass/fail summary. ## Core Features & Use Cases - Automated Test Execution: Finds the active feature's spec-integration-tests directory and runs all tc-*.sh scripts via run-all.sh, or a filtered subset like tc-010 tc-011. - Prerequisite Validation: Warns about missing environment variables (PP, IDENTITY, PG_CONN) and missing tools (curl, jq, psql) before running tests. - Structured Results: Parses the TEST SUMMARY block and displays Passed, Failed, Skipped, and Total counts in a formatted table with failing test details. - Use Case: After generating test scripts with /speckit-scripttest, run this Skill to execute the full integration test suite for your feature and immediately see which test cases failed and why. ## Quick Start Run the integration tests for my current feature spec and show me which test cases passed or failed.

Frequently Asked Questions about speckit-runtests

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

FAQPage Schema
How do I run integration tests for a spec-kit feature?▼

Run this Skill with no arguments to execute all tc-*.sh scripts via run-all.sh in the active feature's spec-integration-tests directory. It locates the feature using check-prerequisites.sh and streams the output as tests run.

How do I run only specific test cases instead of the full suite?▼

Pass TC names as arguments, such as tc-010 tc-011, to run only those cases through run-all.sh. Plain numbers like 10 are expanded to tc-010 automatically.

What environment variables do the integration tests need?▼

The tests rely on PP for HTTP endpoints, IDENTITY for authentication tests, and PG_CONN for database assertions, typically sourced from config.env. Missing variables cause warnings, and related tests will fail.

Why do the integration tests fail with missing tool errors?▼

The scripts require curl for HTTP requests, jq for JSON assertions, and psql for database checks. The Skill warns before running if any of these tools are not found on the system.

What happens if no test scripts exist for the feature?▼

The Skill stops and instructs you to run /speckit-scripttest first to generate the tc-*.sh scripts and run-all.sh in the spec-integration-tests directory.