qa-test-strategy

Define test pyramid targets and map acceptance criteria to test layers.

6|Updated Apr 24, 2026

Search Tags:#qa #acceptance-criteria #risk-analysis #pyramid #test-strategy #contract-tests #test-mapping

Ready to run

npx skills add https://github.com/lookatitude/guild --skill qa-test-strategy-lookatitude

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-test-strategy
Source: https://github.com/lookatitude/guild/tree/main/skills/specialists/qa-test-strategy
Command: npx skills add https://github.com/lookatitude/guild --skill qa-test-strategy-lookatitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA teams decide what kinds of tests a feature needs, how to allocate coverage across unit, integration, contract, and end-to-end levels, and how to map acceptance criteria to the appropriate layer.

Core Features & Use Cases

Define a feature-wide test pyramid with concrete targets per layer (unit, integration, contract, e2e).
Produce a test-strategy.md that documents scope, risks, and the criterion-to-layer map for downstream test writers.
Output explicit out-of-scope decisions to avoid scope creep and ensure focused validation.

Quick Start

Provide a complete test strategy for a feature, outputting test-strategy.md and a risk-to-layer map.

Frequently Asked Questions about qa-test-strategy

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

FAQPage Schema

How do I map acceptance criteria to the correct test pyramid layers?▼

A feature test strategy defines the appropriate test pyramid targets, maps acceptance criteria to specific layers, and documents explicit out-of-scope decisions to guide downstream test writers and ensure focused validation.

What is the best way to define test coverage for an API redesign?▼

Defining test coverage for an API redesign involves applying a test strategy to determine the necessary integration and contract tests, mapping acceptance criteria to those layers, and identifying risky seams for targeted validation.

How do I create a test strategy document that prevents scope creep?▼

You create a test strategy document by outputting explicit out-of-scope decisions alongside the criterion-to-test-layer map, ensuring QA teams maintain focused validation and avoid expanding testing beyond defined feature boundaries.

When do I need contract tests in my test strategy?▼

You need contract tests in your test strategy when mapping acceptance criteria for API changes or feature redesigns, ensuring integration points are validated and functional requirements are satisfied without relying solely on e2e coverage.

Can I use this approach to plan unit and e2e tests for UI work?▼

Yes, you can apply this test strategy approach to UI work to determine the appropriate balance of unit and e2e coverage, mapping functional requirements to the test pyramid while identifying risky seams for targeted validation.