run-tests

Run a project's default test suite and summarize pass/fail results.

Updated Dec 21, 2018
One-click install
npx skills add https://github.com/dhnt/dhnt --skill run-tests-dhnt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/test/run-tests
Command: npx skills add https://github.com/dhnt/dhnt --skill run-tests-dhnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing whether the project test suite is passing and, if it is not, which specific failures need attention first.

Core Features & Use Cases

  • Discovers the correct test command by checking common build/test entry points (Makefile and common package managers) and falling back to language defaults like Go's go test ./....
  • Executes the suite with informative output so progress is visible and results are not obscured by wrappers or overly aggressive flags.
  • Reports failures clearly and concisely by listing up to five first failures with enough context to reproduce and fix, plus exact commands for re-running.

Quick Start

Ask your AI to run the project's default test suite and then summarize whether tests passed or failed, including the first few failures and the exact reproduction command for each.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I run a project's default test suite and report actionable failures?

To run a default test suite and report actionable failures, the Skill discovers the correct test command from Makefiles or package managers, executes it with informative output, and reports up to five first failures with exact reproduction commands.

How does test execution handle race detection and coverage?

Test execution honors race-detection defaults and runs the suite without skipping coverage, streaming output so progress is visible and results are not obscured by wrappers or overly aggressive flags.

What is the best way to find out why my Go test suite is failing?

The best way to find out why a Go test suite is failing is to run the default test command and report up to five first failures with enough context to reproduce and fix, plus exact commands for re-running.

Does this test execution approach work for local and CI-like scenarios?

Yes, this test execution approach applies to both local and CI-like scenarios where users need actionable feedback from unit, integration, or end-to-end tests with appropriate verbosity.

Can I use this to run tests without a Makefile?

Yes, you can run tests without a Makefile because the Skill checks common build and test entry points and falls back to language defaults like Go's go test ./... when no Makefile is found.

Why does my test suite output obscure which failures need attention first?

Test suite output can obscure failures, but this Skill reports failures clearly and concisely by listing up to five first failures with enough context to reproduce and fix, plus exact commands for re-running.