orchestrating-test-execution

Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".

跳到安装

仓库: jeremylongshore/claude-code-plugins-plus-skills
最近来源活动: 2026年7月17日 22:18
检测到的 SKILL.md 语言: 英语
星标: 2,604
分支: 378

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill orchestrating-test-execution

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

7 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

Test Orchestrator

Overview

Coordinate parallel test execution across multiple test suites, frameworks, and environments. Manages test splitting, worker allocation, result aggregation, and intelligent retry strategies.

Prerequisites

Test runner with parallel execution support (Jest, Vitest, pytest-xdist, Playwright, or JUnit 5)

CI/CD platform configured (GitHub Actions, GitLab CI, CircleCI, or Jenkins)

Test suite with consistent pass rates (flaky tests identified and tagged)

Sufficient CI runner resources for parallel worker count

Test result reporting tool (JUnit XML, Allure, or equivalent)

Instructions

Analyze the existing test suite using Grep and Glob to catalog all test files, their framework, approximate run time, and dependency requirements.

Classify tests into execution tiers:

Tier 1 (Fast): Unit tests with no I/O -- target under 30 seconds total.
Tier 2 (Medium): Integration tests requiring local services -- target under 3 minutes.
Tier 3 (Slow): E2E and browser tests -- target under 10 minutes.

Configure parallel execution for each tier:

Split unit tests across N workers using jest --shard=i/N or pytest -n auto.
Shard E2E tests by test file using Playwright --shard=i/N or Cypress parallelization.
Assign heavier integration tests to dedicated workers with more resources.

Create a CI pipeline configuration that runs tiers in parallel:

Tier 1 and Tier 2 run concurrently on separate jobs.
Tier 3 runs after a fast pre-check gate passes.
Each tier reports results to a unified collection step.

Implement intelligent retry logic for flaky tests:

Tag known flaky tests with @flaky or equivalent marker.
Retry failed tests up to 2 times before marking as failed.
Track flaky test frequency in a log file for triage.

Aggregate results from all parallel workers into a single report:

Merge JUnit XML files from each shard.
Calculate total pass/fail/skip counts and execution time.
Identify the slowest tests for optimization targets.

Write the orchestration configuration to the project's CI config file and validate it with a dry run.

Output

CI pipeline configuration file (.github/workflows/test.yml, , or equivalent)

Test Orchestrator

Overview

Coordinate parallel test execution across multiple test suites, frameworks, and environments. Manages test splitting, worker allocation, result aggregation, and intelligent retry strategies.

Prerequisites

Test runner with parallel execution support (Jest, Vitest, pytest-xdist, Playwright, or JUnit 5)

CI/CD platform configured (GitHub Actions, GitLab CI, CircleCI, or Jenkins)

Test suite with consistent pass rates (flaky tests identified and tagged)

Sufficient CI runner resources for parallel worker count

Test result reporting tool (JUnit XML, Allure, or equivalent)

Instructions

Analyze the existing test suite using Grep and Glob to catalog all test files, their framework, approximate run time, and dependency requirements.

Classify tests into execution tiers:

Tier 1 (Fast): Unit tests with no I/O -- target under 30 seconds total.
Tier 2 (Medium): Integration tests requiring local services -- target under 3 minutes.
Tier 3 (Slow): E2E and browser tests -- target under 10 minutes.

Configure parallel execution for each tier:

Split unit tests across N workers using jest --shard=i/N or pytest -n auto.
Shard E2E tests by test file using Playwright --shard=i/N or Cypress parallelization.
Assign heavier integration tests to dedicated workers with more resources.

Create a CI pipeline configuration that runs tiers in parallel:

Tier 1 and Tier 2 run concurrently on separate jobs.
Tier 3 runs after a fast pre-check gate passes.
Each tier reports results to a unified collection step.

Implement intelligent retry logic for flaky tests:

Tag known flaky tests with @flaky or equivalent marker.
Retry failed tests up to 2 times before marking as failed.
Track flaky test frequency in a log file for triage.

Aggregate results from all parallel workers into a single report:

Merge JUnit XML files from each shard.
Calculate total pass/fail/skip counts and execution time.
Identify the slowest tests for optimization targets.

Write the orchestration configuration to the project's CI config file and validate it with a dry run.

Output

CI pipeline configuration file (.github/workflows/test.yml, , or equivalent)

name	orchestrating-test-execution
description	Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(test:orchestrate-*)
version	1.25.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["testing","orchestrating-test"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

name	orchestrating-test-execution
description	Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(test:orchestrate-*)
version	1.25.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["testing","orchestrating-test"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Error	Cause	Solution
Shard produces zero tests	Uneven test distribution or incorrect shard index	Verify shard count matches actual test file count; use file-based splitting
Worker out of memory	Too many parallel processes on one runner	Reduce `--maxWorkers` or `-n` count; increase runner memory; use `--workerIdleMemoryLimit`
Test ordering dependency	Tests pass in isolation but fail in specific shard order	Add `--randomize` flag; fix shared state leaks; enforce test independence
Result aggregation mismatch	Missing shard results due to job timeout	Set job-level timeouts higher than test timeouts; add result upload as a separate step
CI cache miss slowing startup	Dependencies not cached between parallel jobs	Configure dependency caching per lockfile hash; use a shared setup job

orchestrating-test-execution

安装方式

检查来源文件

Test Orchestrator

Overview

Prerequisites

Instructions

Output

Test Orchestrator

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

orchestrating-test-execution

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Test Orchestrator

Overview

Prerequisites

Instructions

Output

Test Orchestrator

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources