test-orchestrator

Coordinate unit, integration, and end-to-end tests across project components.

Updated Aug 27, 2026

Search Tags:#integration testing #unit testing #e2e testing #test planning #test orchestration #coverage metrics

Ready to run

npx skills add https://github.com/Brownbull/ayni_core --skill test-orchestrator-brownbull

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-orchestrator
Source: https://github.com/Brownbull/ayni_core/tree/main/.claude/skills/test-orchestrator
Command: npx skills add https://github.com/Brownbull/ayni_core --skill test-orchestrator-brownbull

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates testing strategy and execution across all test types. Use when creating test plans, implementing tests (unit/integration/E2E), or enforcing coverage requirements (80% minimum). Applies testing-requirements.md.

Core Features & Use Cases

Test Strategy
- Define test plans
- Coordinate test execution
- Manage test environments
- Track coverage metrics
Test Automation
- Unit test coordination
- Integration test suites
- E2E test scenarios
- Performance testing
Quality Gates
- Define acceptance criteria
- Enforce coverage thresholds
- Block failing builds
- Report quality metrics
Context Maintenance ai-state/active/testing/ ├── test-plans.json # Test strategies ├── coverage.json # Coverage metrics ├── results.json # Test results └── tasks/ # Active test tasks

Quick Start

Create a test plan and start coordinated unit, integration, and end-to-end tests across the project.

Frequently Asked Questions about test-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate unit, integration, and E2E testing across a project?▼

Test orchestration coordinates test execution across unit, integration, and end-to-end suites to ensure project coverage and quality. It manages test plans and tracks metrics across multiple components.

How do I enforce a minimum code coverage threshold in my testing workflow?▼

You enforce minimum code coverage by defining quality gates that block failing builds. The orchestration workflow enforces an 80% minimum coverage threshold and reports quality metrics automatically.

What is the best way to structure test plans and track test results?▼

Structure test plans by defining test strategies and coordinating execution scenarios. The system maintains context by storing test plans, coverage metrics, and results in dedicated JSON files for active tracking.

Can I use a test orchestrator to manage performance testing and E2E test scenarios?▼

Yes, test orchestration manages performance testing and E2E test scenarios through test automation coordination. It handles unit test coordination, integration suites, E2E scenarios, and performance testing workflows.

When should I define quality gates and acceptance criteria for test environments?▼

Define quality gates and acceptance criteria when creating test plans and managing test environments. This blocks failing builds, enforces coverage thresholds, and reports quality metrics during test execution.