coverage

Topics in the source

• Analyze Test Coverage Gaps
• Steps
• 1. Map Application Surface
• 2. Map Existing Tests
• 3. Generate Coverage Matrix
• 4. Prioritize Gaps
• 5. Suggest Test Plan
• 6. Auto-Generate (Optional)

Map all testable surfaces in the application and identify what's tested vs. what's missing. Use the Explore subagent to catalog: Routes/Pages: Scan route definitions (Next.js app/, React Router config, Vue Router, etc.) List all user-facing pages with their paths Components: Identify interactive components (forms, modals, dropdowns, tables) Note components with complex state logic API Endpoints: Scan API route files or backend controllers List all endpoints with their methods User Flows: Identify critical paths: auth, checkout, onboarding, core features Map multi-step workflows Scan all .spec.ts / .spec.js files: Extract which pages/routes are covered (by page.goto() calls) Extract which components are tested (by locator usage) Extract which API endpoints are mocked or hit Count tests per area Rank uncovered areas by business impact: 1. Critical — auth, payment, core features → test first 2. High — user-facing CRUD, search, navigation 3. Medium — settings, preferences, edge cases 4. Low — static pages, about, terms For each gap, recommend: Number of tests needed Which template from templates/ to use Estimated effort (quick/medium/complex) Ask user: "Generate tests for the top N gap

This is an excerpt. Refer to the complete source and its current requirements.