moai-ref-testing-pyramid

Define test pyramid ratios for unit, integration, and end-to-end testing.

Updated Apr 19, 2026

Search Tags:#testing #tdd #integration #e2e #test-patterns #quality-metrics #pyramid

Ready to run

npx skills add https://github.com/windysky/snake-game --skill moai-ref-testing-pyramid-windysky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moai-ref-testing-pyramid
Source: https://github.com/windysky/snake-game/tree/main/.claude/skills/moai-ref-testing-pyramid
Command: npx skills add https://github.com/windysky/snake-game --skill moai-ref-testing-pyramid-windysky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The pyramid testing guide helps software teams design effective test suites by aligning scope, cost, and confidence across unit, integration, and end-to-end tests.

Core Features & Use Cases

Structured test strategy: Defines optimal distribution of tests (unit ~70%, integration ~20%, E2E ~10%) to balance speed and reliability.
Quality targets & verification: Provides guidance on coverage goals, verification steps, and maintenance practices.
Reference patterns & workflow: Documents common testing patterns, red-green-refactor workflow, and TDD/CI concepts for teams.

Quick Start

Review the recommended test pyramid ratios and adapt them to your project's technology stack and risk profile.

Frequently Asked Questions about moai-ref-testing-pyramid

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

FAQPage Schema

What is the ideal test pyramid ratio for balancing unit, integration, and E2E tests?▼

The ideal test pyramid ratio distributes tests as approximately 70% unit, 20% integration, and 10% end-to-end. This distribution balances execution speed and reliability while optimizing overall test coverage and maintenance efforts.

How do I apply TDD patterns to improve my test suite structure?▼

You can apply TDD patterns by following the red-green-refactor workflow documented in the testing guide. This approach structures test planning and verification steps to build reliable, scalable software testing scenarios.

Can I adapt the recommended test pyramid ratios to fit my project's specific technology stack?▼

Yes, you should review the recommended test pyramid ratios and adapt them to your project's specific technology stack and risk profile. This ensures the test strategy aligns scope, cost, and confidence appropriately.

What's the best way to define quality metrics and verification steps for software testing?▼

The best way to define quality metrics is to apply the testing guide's explicit verification steps and coverage goals across unit, integration, and E2E scenarios. This ensures reliable test balance and maintenance.

Why does my test suite have high maintenance costs and slow execution?▼

High maintenance costs and slow execution often indicate an imbalanced test pyramid. Realigning your test distribution towards the recommended 70/20/10 unit, integration, and E2E ratios improves verification speed and reliability.