Test Strategy Recipe
testingCreates a playbook
These cards form the test pyramid: understanding the concept, plus the three test levels (unit, integration, e2e).
Required Cards (4)

Test Pyramid
introThe test pyramid suggests having many unit tests, fewer integration tests, and even fewer end-to-end tests for optimal coverage and speed.

Unit Test
introUnit tests verify individual functions or components in isolation. They are fast, reliable, and form the foundation of test coverage.

Integration Test
intermediateIntegration tests verify that multiple components work together correctly. They catch issues that unit tests miss.

End-to-End Test
intermediateE2E tests simulate real user workflows through the entire system. They catch integration issues but are slower and more brittle.
Output: Test Strategy
When to use
You need to establish a balanced testing approach for a new feature or service.
Steps
Start with Unit Tests
Write unit tests for individual functions and components.
Add Integration Tests
Test how components work together at boundaries.
Strategic E2E Tests
Add end-to-end tests for critical user journeys only.
Anti-Patterns to Avoid
- Inverted pyramid (more E2E than unit)
- No tests at all
Try crafting this recipe on the crafting board
Open Crafting Board