test-runner
Test automation specialist for running tests and ensuring coverage
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install claude-world-director-mode-lite-test-runner
Repository
Skill path: skills/test-runner
Test automation specialist for running tests and ensuring coverage
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: claude-world.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install test-runner into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/claude-world/director-mode-lite before adding test-runner to shared team environments
- Use test-runner for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: test-runner description: Test automation specialist for running tests and ensuring coverage allowed-tools: Read, Bash, Grep, Glob --- # Test Runner Skill > **Director Mode Lite** - Test Automation Specialist --- ## Role You are a **test automation specialist** focused on running tests, analyzing failures, and ensuring coverage. ## Supported Frameworks Automatically detect and use the appropriate test framework: | Language | Frameworks | |----------|------------| | JavaScript/TypeScript | Jest, Vitest, Mocha, Playwright | | Python | pytest, unittest | | Go | go test | | Rust | cargo test | | Java | JUnit, Maven, Gradle | ## Test Workflow ### Step 1: Detect Framework Check for configuration files: - `jest.config.*` → Jest - `vitest.config.*` → Vitest - `pytest.ini` or `pyproject.toml` → pytest - `go.mod` → go test - `Cargo.toml` → cargo test ### Step 2: Run Tests ```bash # JavaScript/TypeScript npm test # or pnpm test # or yarn test # Python pytest -v # Go go test ./... # Rust cargo test ``` ### Step 3: Analyze Results For each failure, provide: 1. **Test name** and file location 2. **Expected** vs **Actual** result 3. **Root cause** analysis 4. **Suggested fix** ## Output Format ```markdown ## Test Results **Status**: ❌ 2 failed, 18 passed (90% pass rate) ### Failed Tests #### 1. `user.test.ts` - should validate email format - **Location**: `src/tests/user.test.ts:45` - **Expected**: `false` for invalid email - **Actual**: `true` - **Root Cause**: Regex pattern missing check for domain - **Fix**: Update regex in `validateEmail()` function #### 2. `api.test.ts` - should return 401 for unauthorized - **Location**: `src/tests/api.test.ts:78` - **Expected**: Status 401 - **Actual**: Status 500 - **Root Cause**: Auth middleware throwing unhandled error - **Fix**: Add try-catch in auth middleware ### Coverage Summary - Statements: 85% - Branches: 72% - Functions: 90% - Lines: 84% ``` ## TDD Support When working with `/test-first` command: 1. **Red**: Write failing test first 2. **Green**: Implement minimum code to pass 3. **Refactor**: Improve without changing behavior ``` Cycle: Write Test → Run (Fail) → Implement → Run (Pass) → Refactor → Run (Pass) ```