run-tests

Execute test suites and report results. Use when validating code functionality.

⭐8stars🔀4forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The run-tests Claude skill automates the execution of software test suites to ensure code reliability and functionality. By supporting various frameworks like Mojo and pytest, it provides developers with detailed reports on pass/fail status, execution times, and failure diagnostics, making it an essential tool for maintaining high software quality and catching regressions early.

Use Cases

  • Pre-commit validation: Automatically run test suites before committing code to ensure that new changes do not break existing functionality.
  • Regression testing: Execute full or partial test suites after significant refactoring to verify that the system still behaves as expected.
  • Bug fix verification: Run specific test files or verbose test commands to confirm that a reported issue has been resolved and to analyze failure details if it persists.
  • Continuous Integration support: Generate structured test reports including coverage metrics and execution time to monitor the health of the codebase over time.
namerun-tests
description"Execute test suites and report results. Use when validating code functionality."
mcp_fallbacknone
categorytesting
tier1
user-invocablefalse

Run Tests

Execute test suites to verify code functionality and identify regressions or failures.

When to Use

  • Pre-commit validation
  • Running tests after changes
  • Verifying test suite passes
  • Generating test reports

Quick Reference

# Run all tests with Mojo
pixi run mojo test -I . tests/

# Run specific test file
mojo test -I . tests/shared/core/test_example.mojo

# Run with verbose output
mojo test -I . tests/ -v

# Python pytest
pytest tests/
pytest tests/ -v --tb=short

Workflow

  1. Set up test environment: Ensure all dependencies installed
  2. Select tests: Choose which test suite or specific tests to run
  3. Execute tests: Run test runner with appropriate options
  4. Review results: Check pass/fail status and output
  5. Debug failures: Investigate and fix failing tests

Output Format

Test results:

  • Total tests run
  • Passed/failed/skipped counts
  • Failure details (assertion message, stack trace)
  • Execution time per test
  • Test coverage metrics (if applicable)

References

  • See generate-tests skill for creating tests
  • See calculate-coverage skill for coverage analysis
  • See CLAUDE.md > TDD in Key Development Principles