devteam-test
npx machina-cli add skill michael-harris/devteam/devteam-test --openclawCurrent session: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session"
Active sprint: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "active_sprint" 2>/dev/null || echo "None"
Failure count: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "consecutive_failures" 2>/dev/null || echo "0"
DevTeam Test Command
Command: /devteam:test [target] [options]
Coordinate test writing and execution across the project. Launches the Test Coordinator to orchestrate language-specific test writers and verification agents.
Usage
# Write tests for current task
/devteam:test
# Write tests for specific files
/devteam:test "src/api/auth.ts"
# Write specific test types
/devteam:test --type unit
/devteam:test --type integration
/devteam:test --type e2e
# Write tests for a scope
/devteam:test --scope "src/services/"
# Run existing tests and fill coverage gaps
/devteam:test --coverage
/devteam:test --coverage --threshold 80
# Cost-optimized
/devteam:test --eco
Options
| Option | Description |
|---|---|
--type <type> | Test type: unit, integration, e2e, all |
--scope <path> | Limit to specific files/directories |
--coverage | Analyze coverage and fill gaps |
--threshold <pct> | Coverage threshold percentage (default: 80) |
--eco | Cost-optimized execution |
Your Process
Phase 0: Initialize Session
source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
source "${CLAUDE_PLUGIN_ROOT}/scripts/events.sh"
SESSION_ID=$(start_session "/devteam:test $*" "test")
log_session_started "/devteam:test $*" "test"
Phase 1: Launch Test Coordinator
Delegate to the quality:test-coordinator agent, which will:
- Analyze target code to determine test needs
- Select appropriate test writers based on language
- Coordinate unit, integration, and e2e test writing
- Run tests and verify they pass
- Report coverage metrics
const result = await Task({
subagent_type: "quality:test-coordinator",
prompt: `Test coordination request:
Target: ${target || 'current task files'}
Type: ${type || 'all'}
Scope: ${scope || 'auto-detect'}
Coverage mode: ${coverageMode}
Threshold: ${threshold || 80}
Coordinate test writers to produce:
1. Unit tests for individual functions/methods
2. Integration tests for component interactions
3. E2E tests for critical user flows
4. Edge case and error handling tests
5. Coverage report and gap analysis`
})
Phase 2: Verification
- Run all generated tests
- Verify tests pass
- Check coverage meets threshold
- Report any flaky tests
Phase 3: Completion
log_session_ended('completed', 'Test writing complete')
end_session('completed', 'Success')
See Also
/devteam:review- Code review before testing/devteam:implement- Implement features to test/devteam:status- Check test progress
Source
git clone https://github.com/michael-harris/devteam/blob/main/skills/devteam-test/SKILL.mdView on GitHub Overview
devteam-test coordinates test writing and execution across the project. It launches the Test Coordinator to orchestrate language-specific test writers and verification agents, aligning unit, integration, and e2e tests and ensuring full code coverage.
How This Skill Works
Phase 0 initializes the test session. Phase 1 delegates to quality:test-coordinator to analyze the target, assign language-appropriate test writers, coordinate unit/integration/e2e tests, and generate a coverage report. Phase 2 runs tests, verifies results, and flags flaky tests; then Phase 3 logs completion.
When to Use It
- Starting tests for a new task or feature
- Writing tests for a specific file or a defined scope
- Coordinating unit, integration, and E2E tests across languages
- Ensuring coverage gaps are identified and coverage is improved
- Opting for cost-optimized test runs with --eco
Quick Start
- Step 1: Run /devteam:test with your target or options
- Step 2: The system delegates to quality:test-coordinator to craft tests
- Step 3: Review test results and coverage metrics; adjust scope/threshold as needed
Best Practices
- Clearly define target and scope before invoking /devteam:test
- Use --type to specify unit, integration, or e2e tests
- Use --scope to restrict to specific files or directories
- Run with --coverage to identify gaps and drive testing effort
- Set a --threshold and consider --eco for cost-conscious runs
Example Use Cases
- Write unit tests for a new authentication module
- Create integration tests for the user service interactions
- Run E2E tests for the login/signup flow
- Scope tests to src/services and verify coverage
- Execute a coverage pass with --threshold 80 and --eco