test-automation-strategy — Claude Code skill: tests and setup
The test-automation-strategy skill shapes a test automation plan, fixes test-pyramid imbalance, and connects checks to CI/CD workflows.
MIT 261 installs ★ 533 updated 2026-10-25
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a claude-codeWhat test-automation-strategy does
The skill helps design or restructure automated testing. It looks for an inverted pyramid, slow suites, order-dependent checks, brittle selectors, and flaky tests. Its testing model uses a 70/20/10 split across unit, integration, and E2E tests, with Page Object Model, Builder, and Factory patterns.
The material covers CI/CD stages, parallel execution, and risk-based test selection. Separate workflows address data isolation, quarantine for unstable tests, and failure analysis across timing, data, and environment issues. Five subagents are coordinated here, including test generation, coverage analysis, and flaky-test investigation.
Parallel runs can fail nondeterministically when tests share state.
What it helps with
- shape a unit, integration, and E2E test pyramid
- find slow and order-dependent checks
- stabilize flaky tests
- connect tests to CI/CD
- select regression checks by risk
Example prompts for the agent
- Review this test suite and propose a 70/20/10 split for unit, integration, and E2E coverage.
- Find flaky tests, inspect timing and data-isolation problems, then outline a stabilization plan.
- Create a CI/CD test pipeline with separate unit, integration, and E2E stages.
How to install test-automation-strategy
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a claude-code2Manually: put the files in place
~/.claude/skills/test-automation-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/test-automation-strategy/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a codex2Manually: put the files in place
.agents/skills/test-automation-strategy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a cursor2Manually: put the files in place
.cursor/skills/test-automation-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install proffesor-for-testing/agentic-qe assets/skills/test-automation-strategy2Manually: put the files in place
.github/skills/test-automation-strategy/SKILL.md1Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a gemini-cli2Platform CLI
gemini skills install https://github.com/proffesor-for-testing/agentic-qe --path assets/skills/test-automation-strategyManually: put the files in place
.devin/skills/test-automation-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about test-automation-strategy
How do I install test-automation-strategy in Claude Code?
Run npx skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy -a claude-code, then check ~/.claude/skills/test-automation-strategy/SKILL.md.
What does test-automation-strategy do?
It designs a test pyramid, applies automation patterns, helps connect tests to CI/CD, and analyzes flaky checks.
What test balance does the skill use?
It uses a 70/20/10 split for unit, integration, and E2E tests. Parallel execution requires isolated test data.
Source text
SKILL.md · MIT
---
name: test-automation-strategy
description: "Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency."
category: testing-methodologies
priority: high
tokenEstimate: 1000
agents: [qe-test-generator, qe-test-executor, qe-coverage-analyzer, qe-flaky-test-hunter, qe-regression-risk-analyzer]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [automation, test-pyramid, page-object, first-principles, ci-cd, flaky-tests]
trust_tier: 3
validation:
schema_path: schemas/output.json
validator_path: scripts/validate-config.json
eval_path: evals/test-automation-strategy.yaml
---
# Test Automation Strategy
<default_to_action>
When designing or improving test automation:
1. DETECT anti-patterns: Ice cream cone? Slow suite? Flaky tests?
2. USE patterns: Page Object Model, Builder pattern, Factory pattern
3. INTEGRATE in CI/CD: Every commit runs tests, fail fast
4. MANAGE flaky tests: Quarantine, fix, or delete - never ignore
**Quick Anti-Pattern Detection:**
- Ice cream cone (many E2E, few unit) → Invert to pyramid
- Slow tests (> 10 min suite) → Parallelize, mock external deps
- Flaky tests → Fix timing, isolate data, or quarantine
- Brittle selectors → Use data-testid, semantic locators
</default_to_action>
## Quick Reference Card
### When to Use
- Building new automation framework
- Improving existing test efficiency
- Reducing flaky test burden
- Optimizing CI/CD pipeline speed
### Anti-Patterns to Detect
| Problem | Symptom | Fix |
|---------|---------|-----|
| Ice cream cone | 80% E2E, 10% unit | Invert pyramid |
| Slow suite | 30+ min CI | Parallelize, prune |
| Flaky tests | Random failures | Quarantine, fix timing |
| Coupled tests | Order-dependent | Isolate data |
| Brittle selectors | Break on CSS change | Use data-testid |
---
## CI/CD Integration
```yaml
name: Test Pipeline
on: [push, pull_request]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm run test:unit -- --coverage
timeout-minutes: 5
- uses: codecov/codecov-action@v3
integration-tests:
needs: unit-tests
runs-on: ubuntu-latest
services:
postgres:
image: postgres:15
steps:
- run: npm run test:integration
timeout-minutes: 10
e2e-tests:
needs: integration-tests
runs-on: ubuntu-latest
steps:
- run: npx playwright test
timeout-minutes: 15
```
---
## Flaky Test Management
```typescript
// Quarantine flaky tests
describe.skip('Quarantined - INC-123', () => {
test('flaky test awaiting fix', () => { /* ... */ });
});
// Agent-assisted stabilization
await Task("Fix Flaky Tests", {
tests: quarantinedTests,
analysis: ['timing-issues', 'data-isolation', 'race-conditions'],
strategies: ['add-waits', 'isolate-fixtures', 'mock-externals']
}, "qe-flaky-test-hunter");
```
---
## Agent-Assisted Automation
```typescript
// Generate tests following pyramid
await Task("Generate Test Suite", {
sourceCode: 'src/',
pyramid: { unit: 70, integration: 20, e2e: 10 },
patterns: ['page-object', 'builder', 'factory'],
framework: 'jest'
}, "qe-test-generator");
// Optimize test execution
await Task("Optimize Suite", {
algorithm: 'johnson-lindenstrauss',
targetReduction: 0.3,
maintainCoverage: 0.95
}, "qe-regression-risk-analyzer");
// Analyze flaky patterns
await Task("Flaky Analysis", {
testHistory: 'last-30-days',
detectPatterns: ['timing', 'data', 'environment'],
recommend: 'stabilization-strategy'
}, "qe-flaky-test-hunter");
```
---
## Agent Coordination Hints
### Memory Namespace
```
aqe/automation/
├── test-pyramid/* - Coverage by layer
├── page-objects/* - Shared page objects
├── flaky-registry/* - Quarantined tests
└── execution-metrics/* - Suite performance data
```
### Fleet Coordination
```typescript
const automationFleet = await FleetManager.coordinate({
strategy: 'test-automation',
agents: [
'qe-test-generator', // Generate pyramid-compliant tests
'qe-test-executor', // Parallel execution
'qe-coverage-analyzer', // Coverage gaps
'qe-flaky-test-hunter', // Flaky detection
'qe-regression-risk-analyzer' // Smart selection
],
topology: 'hierarchical'
});
```
---
## Related Skills
- [tdd-london-chicago](../tdd-london-chicago/) - TDD for unit tests
- [api-testing-patterns](../api-testing-patterns/) - Integration patterns
- [cicd-pipeline-qe-orchestrator](../cicd-pipeline-qe-orchestrator/) - Pipeline integration
- [shift-left-testing](../shift-left-testing/) - Early automation
---
## Remember
**With Agents:** Agents generate pyramid-compliant tests, detect flaky patterns, optimize execution time, and maintain test infrastructure. Use agents to scale automation quality.
## Gotchas
- Agent generates 80% E2E tests and 20% unit tests (inverted pyramid) — explicitly enforce 70/20/10 ratio
- Page Object Model tests become brittle when selectors change — prefer data-testid attributes over CSS selectors
- Flaky tests quarantined but never fixed is technical debt — set a 2-week SLA to fix or delete
- Agent treats test code as second-class — test code needs the same review standards as production code
- Parallel test execution requires test isolation — shared state between tests causes non-deterministic failures
© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe