Prompt · Developer Tools

Test Pyramid Planner

Decides what to cover with unit, integration, and E2E tests for a feature.

Have ready: Describe the feature and its critical paths

Fill in · 6 fields

DESCRIBE THE FEATURETHE FLOWS THAT MUST NEVER BREAK, e.g. CHECKOUT, LOGINFRONTEND / BACKEND FRAMEWORKS, TEST TOOLS AVAILABLEWHAT EXISTS TODAYNDESCRIBE IT IN ONE LINE OR "UNKNOWN"

Your prompt

Plan the test strategy for this feature across the test pyramid.

Feature: [DESCRIBE THE FEATURE]
Critical paths: [THE FLOWS THAT MUST NEVER BREAK, e.g. CHECKOUT, LOGIN]
Stack: [FRONTEND / BACKEND FRAMEWORKS, TEST TOOLS AVAILABLE]
Current coverage: [WHAT EXISTS TODAY]

Deliver:
1. Unit tests: which pure logic to cover, list the functions/modules and the key cases each.
2. Integration tests: which seams to test (API ↔ DB, service ↔ queue, frontend ↔ API contract) and what each test proves.
3. E2E tests: the MINIMAL set, only the critical paths, each mapped to a user journey. Cap it: if you list more than [N], justify each extra one.
4. What NOT to test at each level (and why, e.g. "don't E2E-test validation the unit tests cover").
5. The one test that would have caught my last production incident: [DESCRIBE IT IN ONE LINE OR "UNKNOWN"].

Optimize for signal per minute of CI time, not coverage percentage.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Bug Report Formatter

CLI UX Review

Rollout Planner

Dependency Upgrade Plan

Serialization Chooser

Query Plan Explainer