---
name: analisis-cobertura-tests-playwright
description: Mapea todas las superficies testables de una aplicación web (rutas, componentes, endpoints, flujos de usuario) y las compara con los tests existentes para identificar brechas de cobertura prioritarias. Genera una matriz de cobertura, clasifica los gaps por impacto de negocio y propone un plan de tests con estimación de esfuerzo.
license: MIT
metadata:
  id: d1568ec0
  slug: analisis-cobertura-tests-playwright
  titulo: "Análisis de Cobertura de Tests con Playwright"
  servicio: Web
  categoria_recurso: Web-Desarrollo
  tipo: analisis
  nivel: intermedio
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Playwright, Next.js, React, Vue, Node.js]
  dependencias: [Playwright Pro, Explore subagent]
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-12", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Identifica qué partes de una aplicación web carecen de tests automatizados y las prioriza por impacto de negocio."
    como_lo_hace: "Escanea definiciones de rutas y archivos spec existentes, cruza ambas listas en una matriz y ordena los gaps en 4 niveles de prioridad (crítico, alto, medio, bajo)."
  content_hash: "d1568ec07b26c6360eab6952fc466290ecf7f795fed61e6ac51435063a0c47e3"
  version: 1.0.0
---

# Analyze Test Coverage Gaps

Map all testable surfaces in the application and identify what's tested vs. what's missing.

## Steps

### 1. Map Application Surface

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

### 2. Map Existing Tests

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

### 3. Generate Coverage Matrix

```
## Coverage Matrix

| Area | Route | Tests | Status |
|---|---|---|---|
| Auth | /login | 5 | ✅ Covered |
| Auth | /register | 0 | ❌ Missing |
| Auth | /forgot-password | 0 | ❌ Missing |
| Dashboard | /dashboard | 3 | ⚠️ Partial (no error states) |
| Settings | /settings | 0 | ❌ Missing |
| Checkout | /checkout | 8 | ✅ Covered |
```

### 4. Prioritize Gaps

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

### 5. Suggest Test Plan

For each gap, recommend:
- Number of tests needed
- Which template from `templates/` to use
- Estimated effort (quick/medium/complex)

```
## Recommended Test Plan

### Priority 1: Critical
1. /register (4 tests) — use auth/registration template — quick
2. /forgot-password (3 tests) — use auth/password-reset template — quick

### Priority 2: High
3. /settings (4 tests) — use settings/ templates — medium
4. Dashboard error states (2 tests) — use dashboard/data-loading template — quick
```

### 6. Auto-Generate (Optional)

Ask user: "Generate tests for the top N gaps? [Yes/No/Pick specific]"

If yes, invoke `/pw:generate` for each gap with the recommended template.

## Output

- Coverage matrix (table format)
- Coverage percentage estimate
- Prioritized gap list with effort estimates
- Option to auto-generate missing tests