What problem does it solve?
Web apps often suffer from patchwork verification that wastes time or misses critical risks. This skill provides a principled way to map product risks to a proportional mix of testing types, replacing ad hoc checks with a clear, trade-off-aware plan.
Core Features & Use Cases
- Identify the change scope and the main failure risks.
- Separate what must be prevented from what only needs detection after release.
- Map relevant surfaces: pure logic, UI state behavior, API integration, user-critical flows, and release smoke checks.
- Choose the lightest mix of test types that covers the real risk: unit, integration, end-to-end, visual/regression, and manual checks.
- Call out potential flakiness, slowness, or low-signal areas, and note automation vs. manual work.
- Boundaries: pragmatic coverage; avoid defaulting to end-to-end for everything; minimize maintenance burden.
Quick Start
Analyze a feature, identify risks, and propose a minimal, effective mix of unit, integration, end-to-end, visual, and manual tests.