What is the core principle of this Test Pyramid skill?

The core principle is to test at the lowest level possible that can catch a bug. This ensures that the majority of tests are fast, isolated unit tests, while expensive E2E tests are reserved for critical user journeys.

How does it decide if a test should be an E2E test?

A test only qualifies for E2E if it requires a real browser (e.g., focus management, complex drag-and-drop), covers a critical business flow, has high regression risk, and cannot be effectively tested at a lower level.

What are the recommended performance targets?

Unit tests should run in under 10ms, integration tests in under 100ms, and individual E2E tests should complete within 30 seconds to maintain a fast development loop.

How does this skill handle flaky tests?

It implements a triage protocol: the first flake is watched, the second within a week triggers an investigation, and the third results in the test being fixed or moved to a quarantine state.

Test Pyramid Strategy

Name: Test Pyramid Strategy
Author: nikhillinit

bynikhillinit

安全与测试

Optimizes software quality by enforcing a structured test pyramid and controlling end-to-end test sprawl through strict admission criteria.

关于

The Test Pyramid Strategy skill provides a comprehensive framework for managing testing levels within a repository, ensuring a healthy balance between speed and coverage. It establishes clear boundaries for unit, integration, and E2E tests, targeting an 80/15/5 distribution to prevent slow, flaky test suites. By defining specific performance metrics, selector strategies, and admission criteria for expensive browser tests, this skill helps developers and AI agents maintain a high-velocity CI/CD pipeline while ensuring critical user journeys remain robust and reliable.

主要功能

0 GitHub stars
Defined test distribution targets (80% Unit, 15% Integration, 5% E2E)
Standardized selector strategy prioritizing data-testid and accessibility
Target performance metrics for test execution speed at every level
Strict E2E admission criteria to prevent suite bloat and flakiness
Integrated flake management and automated quarantine protocols

使用场景

Designing a scalable testing architecture for new or existing projects
Reducing CI/CD build times by demoting redundant E2E tests to unit or integration levels
Standardizing automated test generation for AI agents and developer workflows

关于

主要功能

0 GitHub stars
Defined test distribution targets (80% Unit, 15% Integration, 5% E2E)
Standardized selector strategy prioritizing data-testid and accessibility
Target performance metrics for test execution speed at every level
Strict E2E admission criteria to prevent suite bloat and flakiness
Integrated flake management and automated quarantine protocols

使用场景

Designing a scalable testing architecture for new or existing projects
Reducing CI/CD build times by demoting redundant E2E tests to unit or integration levels
Standardizing automated test generation for AI agents and developer workflows