Test Automation Strategy

This one helps you build test automation that doesn't collapse under its own weight. It pushes you toward the test pyramid (70% unit, 20% integration, 10% E2E) instead of the ice cream cone most teams accidentally create. The quick reference card flags common problems like flaky tests and brittle selectors, then shows fixes like quarantining and using data-testid attributes. The CI/CD integration examples are ready to copy, and it coordinates five QE agents to generate tests, hunt down flaky patterns, and optimize execution time. The gotchas section is honest about what goes wrong, like agents generating inverted pyramids or teams quarantining flaky tests forever without fixing them.

skills.sh installs: 256
GitHub stars: 524
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add proffesor-for-testing/agentic-qe --skill test-automation-strategy --agent claude-code

Installs into .claude/skills of the current project.

Files

Test Automation Strategy

<default_to_action> When designing or improving test automation:

DETECT anti-patterns: Ice cream cone? Slow suite? Flaky tests?
USE patterns: Page Object Model, Builder pattern, Factory pattern
INTEGRATE in CI/CD: Every commit runs tests, fail fast
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