skills.rest
pacphi
pacphiCOMMUNITY
Explore all skills by this author →
𝕏@fastnsilverGitHub

test-automation-strategy

Design test automation frameworks with pyramid distribution and CI/CD integration.

6|3|Updated Dec 3, 2025
Search Tags:#CI/CD#automation strategy#testing patterns#test pyramid#page object
One-click install
npx skills add https://github.com/pacphi/ampel --skill test-automation-strategy-pacphi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-automation-strategy
Source: https://github.com/pacphi/ampel/tree/main/.claude/skills/test-automation-strategy
Command: npx skills add https://github.com/pacphi/ampel --skill test-automation-strategy-pacphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured approach to building automated test suites with a focused pyramid, patterns, and CI/CD integration.

Core Features & Use Cases

  • Test pyramid: 70% unit, 20% integration, 10% E2E guidance.
  • Patterns: Page Object, Builder, Factory to reduce duplication.
  • CI/CD integration: Automate tests to run on every change with fast feedback.

Quick Start

Instruction: "Plan a new automation framework with unit-dominant tests and CI integration."

Frequently Asked Questions about test-automation-strategy

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

FAQPage Schema
How do I structure a test automation framework using the test pyramid?▼

The test pyramid distributes tests as 70% unit, 20% integration, and 10% E2E tests. This structure provides fast feedback at lower levels while keeping expensive end-to-end tests minimal, reducing overall suite runtime and maintenance burden.

What patterns reduce duplication in automated test suites?▼

Page Object Model, Builder, and Factory patterns encapsulate UI interactions, test data construction, and object creation respectively. These patterns centralize maintenance, improve readability, and make tests resilient to UI or domain changes.

How do I integrate test automation into CI/CD pipelines?▼

Automate tests to run on every code change by configuring CI/CD workflows to execute unit, integration, and E2E suites at appropriate stages. This provides immediate feedback, catches regressions early, and enforces quality gates before deployment.

What causes flaky tests and how do I prevent them?▼

Flaky tests result from timing issues, external dependencies, and non-deterministic behavior. Prevention involves FIRST principles (Fast, Isolated, Repeatable, Self-validating, Timely), proper waits, mock external services, and consistent test data.

When should I use E2E tests versus unit or integration tests?▼

E2E tests validate critical user workflows across the full stack but run slowly; reserve them for high-value scenarios. Unit tests catch logic errors fast; integration tests verify component interactions. The 70/20/10 ratio balances coverage with execution speed.

Related Skills

Explore More Software Engineering Skills→
89jobrien89jobrien
4

claude-hooks

Configure Claude Code hooks for workflow automation and audit logging.

Community
Intermediate
PaneriVatsalPaneriVatsal

cicd-pipeline-generator

Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI/CD, CircleCI, and Jenkins.

Community
Advanced
vndkubivndkubi

generate-unit-tests

Generate JUnit 5 tests with AssertJ assertions for Java classes.

Community
Advanced
ivegamsftivegamsft

manual-test-strategy

Structure manual testing strategies with templates for exploratory sessions and test classification.

Community
Intermediate