test-runner

Run scoped cargo tests for changed Rust files and summarize results.

5|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill test-runner-effortlessmetrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/EffortlessMetrics/demo-swarm/tree/main/.claude/skills/test-runner
Command: npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill test-runner-effortlessmetrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive and time-consuming task of running tests and summarizing their results, accelerating development feedback cycles and ensuring code quality without manual oversight.

Core Features & Use Cases

  • Scoped Test Execution: Intelligently runs only relevant tests based on changed files (git diff) or provided scope (e.g., cargo test -p <crate>), maximizing efficiency.
  • Comprehensive Reporting: Captures raw test output and generates a concise test_summary.md including overall status (PASS/FAIL), names of failing tests, and top error snippets.
  • Efficiency & Speed: Prioritizes bounded test runs for faster feedback, with a robust fallback for full test suite execution when required.
  • Use Case: During the "Build" phase, automatically execute unit tests for only the Rust crates affected by recent code changes. The Skill then provides an immediate summary of pass/fail status and any critical errors, allowing developers to quickly identify and fix issues.

Quick Start

Execute the test-runner skill to run all tests in the 'my-feature-crate' Rust package and summarize the results in 'test_summary.md'.

Frequently Asked Questions about test-runner

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

FAQPage Schema
How do I run unit tests for only the files I changed in my Rust project?

Test-runner automatically identifies changed files using git diff and executes only relevant tests for affected crates, then generates a summary with pass/fail status and error details in test_summary.md.

Can I automate test execution and reporting in my Rust CI/CD pipeline?

Yes. Test-runner integrates into Build and Gate phases, running scoped or full workspace cargo test commands, capturing output to test_output.log, and producing a concise test_summary.md with failing test names and top error snippets.

What information does the test summary include after running tests?

Test_summary.md reports overall status (PASS/FAIL), names of all failing tests, top error snippets, and counts of passed, failed, skipped, xfailed, and xpassed tests.

How does test-runner handle large test suites in Rust repositories?

Test-runner prioritizes bounded, crate-specific test runs for speed. If scoped tests are insufficient, it falls back to full workspace execution (Flow 3/4) for comprehensive validation.

Does test-runner modify my source code or tests when generating reports?

No. Test-runner only runs tests, captures raw output, generates summaries, and reports failing test names to downstream agents without modifying source or test files.