Easy Test Executor

One-command test runner that auto-detects your project's test framework and executes the full suite with formatted output and exit code reporting.

When to Use This Command

Run this command when...

• You need to quickly run all tests without remembering framework-specific CLI syntax
• You want a unified test execution experience across JavaScript, Python, Go, or Rust projects
• You are validating changes before committing and need a fast pass/fail summary

Avoid this command when...

• You need to run a single specific test file or test case with custom flags
• Your project requires environment-specific setup before tests can execute

Quick Start

Copy
# .claude/commands/easy-test-executor.md
---
allowed-tools: ["Bash"]
---
Detect the test framework in this project and run the full test suite.
Report pass/fail counts and exit code.

Example usage:

/easy-test-executor

Example output:

Detected: Jest (package.json)
Running: npx jest --verbose

Tests:  42 passed, 0 failed
Time:   3.21s
Exit:   0

Core Concepts

Concept	Description
Auto-detection	Scans package.json, pytest.ini, go.mod, Cargo.toml
Framework map	Maps detected config to the correct test command
Exit codes	Returns 0 for all pass, 1 for any failure
Verbose mode	Streams test output in real-time to the terminal

Project Root
  |
  +-- package.json? --> npm test / npx jest
  +-- pytest.ini?   --> python -m pytest
  +-- go.mod?       --> go test ./...
  +-- Cargo.toml?   --> cargo test

Configuration

Option	Default	Description
framework	auto	Override auto-detection with explicit framework
verbose	true	Show individual test names in output
bail	false	Stop on first failure
coverage	false	Include coverage report
timeout	120s	Maximum wall-clock time before aborting

Best Practices

1. Let auto-detection work first -- only override the framework when your project has multiple test configs and the wrong one is selected.
2. Run before every commit -- pair this command with a pre-commit hook or use it as a final gate before staging changes.
3. Check exit codes -- downstream commands can depend on the exit code to decide whether to proceed.
4. Keep tests fast -- if execution takes more than 60 seconds, consider splitting into unit and integration suites.
5. Review verbose output -- skimming test names helps catch accidentally disabled or duplicated tests.

Common Issues

1. "No test framework detected" -- Ensure your config file (package.json, pytest.ini, etc.) is in the project root. If it is nested, pass the framework explicitly.
2. Tests pass locally but fail here -- Environment variables or database connections may be missing. Check that .env files are loaded or mock external services.
3. Timeout exceeded -- Long-running integration tests can hit the default 120s limit. Increase the timeout or exclude slow tests with a tag filter.