Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From test-orchestrator
Generates test orchestration configs for staged workflows with dependencies, parallel execution, smart selection of affected tests, retries, and CI/CD optimization.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin test-orchestratorHow this command is triggered — by the user, by Claude, or both
Slash command
/test-orchestrator:orchestrateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Test Orchestrator Orchestrate complex test execution workflows with dependency management, parallel execution, smart test selection, and optimized CI/CD integration. ## What You Do 1. **Test Workflow Design**: Create test execution graphs with dependencies 2. **Parallel Execution**: Identify and run independent tests in parallel 3. **Smart Selection**: Run only affected tests based on code changes 4. **Dependency Management**: Ensure tests run in correct order 5. **Resource Optimization**: Balance test execution across available resources ## Output Example
/flow-test-strategy-executionOrchestrates test strategy execution for unit/integration/e2e/regression tests, validating coverage, triaging defects, and analyzing regressions.
/coverGenerates and runs unit, integration (docker-compose/testcontainers), and Playwright E2E test suites for existing code. Analyzes coverage gaps, spawns parallel agents per tier, executes tests, and heals failures up to 3 times.
/testExecutes intelligent tests based on PR changes or patterns/modifiers, runs them via ./run_tests.sh, analyzes/fixes results, and verifies GitHub CI status.
/testRuns unit, integration, E2E test suites with framework detection (Jest/Vitest/pytest/Go/Playwright/Cypress/Selenium), generates coverage reports and badges.
/setup-testsSets up testing infrastructure: auto-detects project type, installs frameworks like Vitest/pytest/Playwright, creates unit/integration/E2E tests, generates /test command.
/tdd-cycleOrchestrates strict red-green-refactor TDD cycle for a feature/module, writing tests/code to .tdd-cycle/ with checkpoints and coverage checks. Supports --incremental, --suite, --coverage flags.
Share bugs, ideas, or general feedback.
Orchestrate complex test execution workflows with dependency management, parallel execution, smart test selection, and optimized CI/CD integration.
// test-orchestration.config.js
module.exports = {
stages: [
{
name: 'unit-tests',
parallel: true,
tests: ['**/*.unit.test.js'],
maxWorkers: 4
},
{
name: 'integration-tests',
dependsOn: ['unit-tests'],
parallel: true,
tests: ['**/*.integration.test.js'],
maxWorkers: 2
},
{
name: 'e2e-tests',
dependsOn: ['integration-tests'],
parallel: false,
tests: ['**/*.e2e.test.js']
}
],
smartSelection: {
enabled: true,
algorithm: 'affected-files',
fallback: 'all-tests'
},
retries: {
flaky: 2,
timeout: 1
}
};
# Smart test selection based on changed files
$ test-orchestrator run --changed
Analyzing changes...
Modified files: 3
Affected tests: 47 (4% of total)
Executing test plan:
Stage 1: Unit Tests (32 tests, parallel)
Completed in 12s
Stage 2: Integration Tests (12 tests, parallel)
Completed in 28s
Stage 3: E2E Tests (3 tests, sequential)
Completed in 45s
Total: 47 tests in 85s (instead of 18m for full suite)