Coverage

alirezarezvani/claude-skills/engineering-team/playwright-pro/skills/coverage

作者 alirezarezvani19392f7a0826無授權條款27K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫5 週前更新

Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".

AI 產生的概覽

將應用程式的可測試面與現有測試相互對照,找出涵蓋缺口並提出依優先順序排列的測試計畫。

功能
此技能會盤點應用程式的路由、元件、API 端點與使用者流程,再掃描現有測試檔案,確認實際受到測試的部分。它會產出涵蓋矩陣表格、涵蓋率估算,以及依業務影響排序的缺口清單。它也能提出所需測試數量、範本建議與工作量估算,並可選擇為最優先的缺口觸發測試產生。
適用情境
當有人詢問測試涵蓋率、哪些尚未測試、涵蓋缺口、缺少的測試或需要測試什麼時使用。適合希望在補寫測試前,取得未涵蓋路由、元件或端點結構化檢視的團隊。
執行需求
僅為說明內容,未附帶指令碼。它依賴 Explore 子代理掃描程式碼庫,並引用 templates/ 目錄中的範本;可選的自動產生會呼叫 /pw:generate 指令。

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: Critical1. /register (4 tests) — use auth/registration template — quick2. /forgot-password (3 tests) — use auth/password-reset template — quick
### Priority 2: High3. /settings (4 tests) — use settings/ templates — medium4. 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

來源與署名

來源:alirezarezvani/claude-skills位於engineering-team/playwright-pro/skills/coverage提交19392f7

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架