How do I install the QA Split Testing Levels Pyramid skill?

Run npx skillmds@latest add testomatio/qa-split-testing-levels-pyramid in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is QA Split Testing Levels Pyramid safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Split Testing Levels Pyramid?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is QA Split Testing Levels Pyramid free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published QA Split Testing Levels Pyramid?

testomatio (@testomatio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA Split Testing Levels Pyramid by testomatio

Name: QA Split Testing Levels Pyramid
Author: testomatio

QA Split Testing Levels Pyramid

Apply the testing pyramid to a feature — divide test scenarios across levels (unit, integration, e2e), assign each scenario to the cheapest sufficient level, and produce a coverage split per level. Use when asked "unit, integration or e2e?", "what level should this test be?", "how should we test this feature?", "what test coverage do we need?", or to apply the test pyramid to a feature or project.

testomatio 9d9b8c9 2.5 KB Updated Sep 17, 2026

File contents

QA Split Testing Levels — Test Pyramid

Applies the testing pyramid to a feature: each scenario goes to the cheapest level that can still catch its failure. Input: a feature description, or risk scenarios from a prior QA analysis.

Testing levels

Default layers, bottom to top:

unit + integration
e2e
manual

A layer can hold several kinds of tests with separate runners: e2e api / e2e web / e2e mobile. Other testing layers a project may have instead: component, functional, contract, visual. Take the testing layers and kinds from the project; use the default only when the scan finds nothing.

Workflow

Inventory existing tests with the scan-automation-project skill.
Detect the project's testing layers and the kinds of tests inside them.
Assign each scenario to the lowest layer that catches its failure, and to a kind within it.
Recommend a coverage split per layer and kind.

Rules

Do not recommend manual verification for scenarios already covered by automated tests.
Explain why a scenario cannot sit at a lower layer when assigning it upward.
A kind never covers another kind of the same layer: e2e web does not cover e2e api.
Generalize existing automated scenarios; expand only when the user asks.

Output

Section 📐 Testing levels: the layers and kinds used, when they differ from the default.
Section ☑️ What is already tested: number and scope of existing tests per layer and kind.
Section 🧪 Testing plan: scenario → layer and kind (e2e / api), with reasoning.
When the environment can render charts, add a pie chart or test pyramid: test count and share per layer and kind. Skip the diagram in plain terminal output.
For manual items: how to verify (action → expected result).

Next actions

Offer after the plan:

Write manual test cases or a checklist → qa-write-test-cases skill.
Automate manual cases into autotests → automate-manual-test-cases skill.
Map tests to source files for change-aware runs → qa-test-code-coverage skill.

---name: qa-split-testing-levels-pyramiddescription: Apply the testing pyramid to a feature — divide test scenarios across levels (unit, integration, e2e), assign each scenario to the cheapest sufficient level, and produce a coverage split per level. Use when asked "unit, integration or e2e?", "what level should this test be?", "how should we test this feature?", "what test coverage do we need?", or to apply the test pyramid to a feature or project.license: MIT---# QA Split Testing Levels — Test PyramidApplies the testing pyramid to a feature: each scenario goes to the cheapest level that can still catch its failure.Input: a feature description, or risk scenarios from a prior QA analysis.## Testing levelsDefault layers, bottom to top:- **unit + integration**- **e2e**- **manual**A layer can hold several kinds of tests with separate runners: `e2e api` / `e2e web` / `e2e mobile`.Other testing layers a project may have instead: component, functional, contract, visual.**Take the testing layers and kinds from the project; use the default only when the scan finds nothing.**## Workflow1. Inventory existing tests with the `scan-automation-project` skill.2. Detect the project's testing layers and the kinds of tests inside them.3. Assign each scenario to the lowest layer that catches its failure, and to a kind within it.4. Recommend a coverage split per layer and kind.## Rules- Do not recommend manual verification for scenarios already covered by automated tests.- Explain why a scenario cannot sit at a lower layer when assigning it upward.- A kind never covers another kind of the same layer: `e2e web` does not cover `e2e api`.- Generalize existing automated scenarios; expand only when the user asks.## Output- Section `📐 Testing levels`: the layers and kinds used, when they differ from the default.- Section `☑️ What is already tested`: number and scope of existing tests per layer and kind.- Section `🧪 Testing plan`: scenario → layer and kind (`e2e / api`), with reasoning.- When the environment can render charts, add a pie chart or test pyramid: test count and share per layer and kind. Skip the diagram in plain terminal output.- For manual items: how to verify (`action → expected result`).## Next actionsOffer after the plan:- Write manual test cases or a checklist → `qa-write-test-cases` skill.- Automate manual cases into autotests → `automate-manual-test-cases` skill.- Map tests to source files for change-aware runs → `qa-test-code-coverage` skill.

Frequently asked questions