software-test-execution

Execute scoped tests across frameworks and report structured pass/fail results.

902|58|Updated May 31, 2012
One-click install
npx skills add https://github.com/stencila/stencila --skill software-test-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-test-execution
Source: https://github.com/stencila/stencila/tree/main/.stencila/skills/software-test-execution
Command: npx skills add https://github.com/stencila/stencila --skill software-test-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Running the right tests after writing or refactoring code is error-prone: you must identify the correct test framework, construct a scoped command, and interpret raw output. This Skill automates test execution for a TDD slice and returns a clear structured pass/fail report.

Core Features & Use Cases

  • Framework Discovery: Detects the test framework from build files like Cargo.toml, package.json, pyproject.toml, go.mod, and more, then constructs a scoped test command.
  • Structured Result Parsing: Parses output from pytest, cargo test, vitest, go test, RSpec, and JUnit into counts of passed, failed, and skipped tests with failure details.
  • Failure Diagnosis: Distinguishes compilation errors, missing dependencies, timeouts, and zero-test runs, reporting each clearly without modifying any code.
  • Use Case: After implementing a new token validation module in Rust, run cargo test -p my-auth through this Skill to get a structured report showing 4 passed and 0 failed tests, ready for the next TDD step.

Quick Start

Run the tests for the current slice and report whether they passed or failed with a structured summary.

Frequently Asked Questions about software-test-execution

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

FAQPage Schema
How do I run only the tests relevant to my code change?

Provide the test files or target packages, and the Skill constructs a scoped command such as `cargo test -p <crate>` or `pytest <test-file>`. It never runs the full suite when scoping is possible, keeping feedback fast.

How to detect which test framework a project uses?

The Skill searches for build files like Cargo.toml, go.mod, package.json, pyproject.toml, pom.xml, and Gemfile, then maps each to its default test command. It also checks Makefiles and CI configs for canonical test commands.

Does this test execution skill support Rust and Python?

Yes, it supports Rust via cargo test, Python via pytest, Go via go test, JavaScript/TypeScript via vitest or jest, plus Java, Ruby, Elixir, Swift, C#, R, and C/C++. Parsing patterns for each framework's output format are included in the references.

What happens when tests fail due to compilation errors?

Compilation or collection errors, such as Rust error[E...] codes or Python SyntaxErrors, are reported as a Fail result with the full error details included. The Skill does not attempt to fix the errors; it only executes and reports.

Why does a test run report pass when zero tests executed?

If the exit code is 0 but zero tests ran, the result is technically Pass but flagged prominently as suspicious. This usually means the test filter matched nothing, indicating stale test file paths or incorrect scoping.

Can this skill write or fix failing tests?

No, it only reads, executes, and reports test results. It does not write or modify any code or test files; fixing failures is left to the upstream agent or developer.