moai-ref-testing-pyramid

Codify testing pyramid targets and patterns for unit, integration, and E2E tests.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-ref-testing-pyramid-gkswls5006-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-testing-pyramid
Source: https://github.com/gkswls5006-web/last-todo/tree/main/.claude/skills/moai-ref-testing-pyramid
Command: npx skills add https://github.com/gkswls5006-web/last-todo --skill moai-ref-testing-pyramid-gkswls5006-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to structure tests effectively, leading to slow feedback, flaky results, and unclear ownership. This skill codifies a reference testing pyramid to guide decision-making on where to invest effort for fast, reliable tests.

Core Features & Use Cases

  • Defines unit/integration/E2E distribution targets and rationale based on risk and maintenance.
  • Provides common test patterns (AAA, mock/stub, snapshot, property-based, boundary value) and guidance on when to apply them.
  • Offers governance prompts for TDD workflows, code reviews, and quality metrics to track progress.

Quick Start

Review your project’s existing tests and align them to the pyramid targets by ratio, patterns, and coverage metrics.

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 testing pyramid and how does it structure unit, integration, and E2E tests?

The testing pyramid structures tests by distributing effort across unit, integration, and E2E layers based on risk. It defines distribution targets and coverage goals to ensure fast, reliable test feedback and clear ownership.

How do I apply TDD workflow patterns and governance during code reviews?

Apply TDD governance by using structured prompts during code reviews and QA planning. This ensures tests follow recommended patterns, meet coverage metrics, and align with defined unit, integration, and E2E distribution targets.

When should I use mock, stub, snapshot, or property-based testing patterns?

Use mock, stub, snapshot, property-based, and boundary value patterns based on specific test scenarios and risk levels. The testing pyramid guides pattern selection to maximize reliability and reduce flaky results.

How do I set coverage goals and quality metrics for different testing contexts?

Set coverage goals by aligning them to the testing pyramid's unit, integration, and E2E targets specific to your project context. Track quality metrics through governance prompts to monitor progress and maintain reliable test distributions.

Why does my test suite have slow feedback and flaky results?

Slow feedback and flaky results often stem from poorly structured tests. Realign your suite to the testing pyramid by adjusting unit, integration, and E2E ratios, applying recommended patterns, and tracking coverage metrics to improve reliability.