| name | test-runner |
| description | Run and interpret test suites across frameworks: Jest, Vitest, pytest, Mocha, tap. Use when: running tests, debugging test failures, generating coverage reports, writing test fixtures, or setting u... |
| category | development |
| maturity | stable |
| tags | ["test-execution","coverage","flaky-tests","framework-detection","pytest"] |
test-runner
Run and interpret test suites across frameworks: Jest, Vitest, pytest, Mocha, tap. Use when: running tests, debugging test failures, generating coverage reports, writing test fixtures, or setting up test infrastructure for a project.
Usage
Run Tests
bash scripts/run-tests.sh [path]
Auto-detects framework from project files. Pass optional path to scope test run.
Coverage Report
bash scripts/coverage-report.sh [path]
Runs tests with coverage and summarizes results.
Detect Flaky Tests
bash scripts/flaky-detector.sh [path] [runs]
Runs test suite multiple times (default: 5) and reports tests with inconsistent results.
When to Use
- Running tests in an unfamiliar project (auto-detects framework)
- Debugging test failures — scripts parse output for actionable info
- Checking coverage before a PR
- Investigating flaky tests that pass/fail intermittently
- Setting up test infrastructure for a new project
Framework Detection
Priority order:
vitest.config.* → Vitestjest.config.* or "jest" in package.json → Jest.mocharc.* or "mocha" in package.json → Mocha"tap" in package.json → tappytest.ini / pyproject.toml with [tool.pytest] / setup.cfg with [tool:pytest] → pytest- Fallback:
npm test if package.json exists, python -m pytest if .py test files exist
Resources
scripts/run-tests.sh — Universal test runner with framework detectionscripts/coverage-report.sh — Coverage reporterscripts/flaky-detector.sh — Flaky test detectorreferences/framework-detection.md — Detection logic detailsreferences/assertion-patterns.md — Common assertion patterns across frameworksreferences/mocking-patterns.md — Mocking/stubbing patterns
