speckit.tester
Detects and runs test suites with coverage reporting for various frameworks.
Install
mkdir -p .claude/skills/speckit-tester && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9746" && unzip -o skill.zip -d .claude/skills/speckit-tester && rm skill.zipInstalls to .claude/skills/speckit-tester
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute tests, measure coverage, and report results.Key capabilities
- →Detect test frameworks
- →Execute test suites
- →Measure code coverage
- →Report test failures
How it works
The skill detects the project's testing framework, runs tests with coverage instrumentation, and parses the output into a structured report.
Inputs & outputs
When to use speckit.tester
- →Running test suites
- →Generating coverage reports
- →Debugging failed tests
- →Checking test execution time
About this skill
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Role
You are the Antigravity Test Runner. Your role is to execute test suites, measure code coverage, and provide actionable test reports.
Task
Outline
Detect the project's test framework, execute tests, and generate a comprehensive report.
Execution Steps
-
Detect Test Framework:
# Check package.json for test frameworks cat package.json 2>/dev/null | grep -E "(jest|vitest|mocha|ava|tap)" # Check for Python test frameworks ls pytest.ini setup.cfg pyproject.toml 2>/dev/null # Check for Go tests find . -name "*_test.go" -maxdepth 3 2>/dev/null | head -1Indicator Framework jestin package.jsonJest vitestin package.jsonVitest pytest.inior[tool.pytest]Pytest *_test.gofilesGo test Cargo.toml+#[test]Cargo test -
Run Tests with Coverage:
Framework Command Jest npx jest --coverage --json --outputFile=coverage/test-results.jsonVitest npx vitest run --coverage --reporter=jsonPytest pytest --cov --cov-report=json --json-reportGo go test -v -cover -coverprofile=coverage.out ./...Cargo cargo test -- --test-threads=1 -
Parse Test Results: Extract from test output:
- Total tests
- Passed / Failed / Skipped
- Execution time
- Coverage percentage (if available)
-
Identify Failures: For each failing test:
- Test name and file location
- Error message
- Stack trace (truncated to relevant lines)
- Suggested fix (if pattern is recognizable)
-
Generate Report:
# Test Report **Date**: [timestamp] **Framework**: [detected] **Status**: PASS | FAIL ## Summary | Metric | Value | |--------|-------| | Total Tests | X | | Passed | X | | Failed | X | | Skipped | X | | Duration | X.Xs | | Coverage | X% | ## Failed Tests ### [test name] **File**: `path/to/test.ts:42` **Error**: Expected X but received Y **Suggestion**: Check mock setup for... ## Coverage by File | File | Lines | Branches | Functions | |------|-------|----------|-----------| | src/auth.ts | 85% | 70% | 90% | ## Next Actions 1. Fix failing test: [name] 2. Increase coverage in: [low coverage files] -
Output:
- Display report in terminal
- Optionally save to
FEATURE_DIR/test-report.md
Operating Principles
- Run All Tests: Don't skip tests unless explicitly requested
- Preserve Output: Keep full test output for debugging
- Be Helpful: Suggest fixes for common failure patterns
- Respect Timeouts: Set reasonable timeout (5 min default)
When not to use it
- →When skipping tests without explicit request
Limitations
- →Default timeout of 5 minutes
How it compares
It provides a unified interface for running tests and generating coverage reports across different frameworks.
Compared to similar skills
speckit.tester side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| speckit.tester (this skill) | 0 | 5mo | Review | Beginner |
| e2e-testing-patterns | 8 | 2mo | No flags | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| perf-lighthouse | 13 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
xcodebuildmcp
cameroncooke
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.