skills.rest
marcocelone
marcoceloneCOMMUNITY
Explore all skills by this author →
GitHub

test-strategy

Assigns test scenarios to optimal test pyramid layers across unit, API, component, and E2E.

1|Updated Jul 12, 2026
Search Tags:#test automation#unit testing#pytest#test strategy#e2e testing#test pyramid#qa planning
One-click install
npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill test-strategy-marcocelone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/marcocelone/demo-python-ai-agent-project/tree/main/.claude/skills/test-strategy
Command: npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill test-strategy-marcocelone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often over-test at the E2E layer, creating slow, brittle suites shaped like an ice cream cone instead of a pyramid. This Skill analyzes test scenarios and assigns each one to the cheapest layer that adequately covers it. ## Core Features & Use Cases - Layer Assignment: Classifies scenarios as Unit, API/Integration, Component, or E2E using explicit decision rules grounded in backend and frontend source code. - Anti-Pattern Detection: Flags misallocated tests such as input validation or API error codes tested at E2E, and missing E2E coverage for critical flows. - Use Case: After generating test scenarios for a booking feature, run this Skill to produce docs/test-strategy.md with a distribution table, per-scenario layer assignments with source file references, and rationale for contested decisions, ready for the test generation step. ## Quick Start Ask the agent to analyze the booking management feature and assign each test scenario to the right test pyramid layer in docs/test-strategy.md.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I decide which test pyramid layer a scenario belongs to?▼

Apply decision rules based on what the scenario exercises: pure functions without I/O go to unit tests, backend business rules and API contracts go to API/integration tests, single-component rendering goes to component tests, and multi-page journeys go to E2E. When in doubt, push the test to the lowest adequate layer.

What is the test pyramid and why avoid E2E-heavy suites?▼

The test pyramid recommends many fast unit tests at the base, fewer API and component tests in the middle, and few E2E tests at the top. An E2E-heavy suite (ice cream cone) is slow, flaky, and expensive to maintain while still missing low-level coverage.

Which tests should stay at the E2E layer?▼

Keep E2E tests for critical multi-page user journeys and full-stack flows that cannot be verified at lower layers, such as a complete ticket booking flow. Input validation, API error codes, and pure logic should be pushed down to API or unit tests.

Can critical business rules be tested at multiple layers?▼

Yes, defense-in-depth is encouraged for critical rules. A booking rule can be verified with fast unit tests for logic, API tests for contract enforcement, and one E2E test confirming the end-to-end behavior.

What inputs does a test strategy analysis need?▼

It needs a scenario list (docs/test-scenarios.md), domain and API documentation, and access to backend services/controllers and frontend components to justify assignments. Existing tests are reviewed to detect anti-patterns like validation tested only at E2E.

Related Skills

Explore More Software Engineering Skills→
mahg-esmahg-es
3

test-case

Generate traceable test cases from requirements and user stories.

Official
Advanced
MediSolveAIDevMediSolveAIDev

write-test-code

Generate pytest and Playwright test code from TC JSON or scenario inputs.

Official
Intermediate
LazyIsEfficientLazyIsEfficient
15

software-design

Enforce domain boundaries and layering to identify internal design problems.

Official
Advanced
a53alia53ali

test-strategy

Design test strategies balancing pyramid layers with risk-based testing.

Community
Intermediate