SkillHub ClubShip Full StackFull StackTesting

run-tests

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

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C4.0

Composite score

4.0

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install mvillmow-projectodyssey-run-tests

Repository

mvillmow/ProjectOdyssey

Skill path: .claude/skills/tier-1/run-tests

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

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack, Testing.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: mvillmow.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install run-tests into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/mvillmow/ProjectOdyssey before adding run-tests to shared team environments
Use run-tests for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: run-tests
description: "Execute test suites and report results. Use when validating code functionality."
mcp_fallback: none
category: testing
tier: 1
---

# 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

```bash
# 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