Software Test Execution
Run scoped tests for a TDD slice, determine the appropriate test framework and command...
Install
npx skills add stencila/stencila --skill software-test-execution -g -a claude-code -y- Repository
- stencila/stencila914
- Category
- Testing
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,638 tokens
- Runs scripts
- No, instructions only
What it does
Run scoped tests for a TDD slice, determine the appropriate test framework and command, and report structured pass/fail results. Use when tests need to be executed after writing, implementing, or refactoring code. Reads test metadata, discovers the test framework if needed, executes the scoped test command, parses output into structured results, and reports whether tests passed or failed. Handles compilation errors, missing dependencies, timeouts, and works with any language and test framework.
Overview
Execute scoped tests for a TDD slice and report structured results. This skill runs only the tests relevant to the current slice, parses the output, and reports a clear pass/fail result with details.
This skill does not write or modify any code or test files. It only reads, executes, and reports.
Required Inputs
This skill requires the following information to operate:
| Input | Required | Description |
|---|---|---|
| Test command | No | Command to run the scoped tests (discovered if not provided) |
| Test files | No | List of test file paths (used to scope the command if needed) |
| Slice scope | No | Description of what the slice covers (for context in the report) |
| Target packages | No | Packages, crates, or directories involved (for command discovery) |
| Slice name | No | Name or identifier of the current slice (for the report header) |
When used standalone, these inputs come from the user or the agent's prompt. When used within a workflow, the workflow's stage prompt will specify how to obtain them.
Outputs
After completing its work, this skill reports:
| Output | Description |
|---|---|
| Result | Whether the tests passed or failed (Pass / Fail) |
| Report | A structured report with counts, failure details, and notes |
Steps
1. Gather test metadata
Ensure the available inputs are collected:
- The test command is the primary input, if present, use it directly
- Test files and target packages are used as fallbacks for constructing a test command if no command is provided
- Slice name and scope provide context for the report
