coverage-matrix-format

name	coverage-matrix-format
description	Coverage matrix table formats, test pyramid analysis templates, and shift-left recommendation structures for QA coverage analysis and test case review. Use when producing AC coverage matrices, manual test case automation coverage tables, coverage gap analysis, shift-left recommendations, test pyramid analysis, or prioritized action plans.
user-invocable	false

Coverage Matrix & Analysis Formats

Mandatory Output Section Order

All coverage analysis responses MUST follow this exact sequence:

1. 📊 ACCEPTANCE CRITERIA COVERAGE MATRIX ← Always First
2. 📋 MANUAL TEST CASE AUTOMATION COVERAGE ← Always Second
3. 🔍 COVERAGE GAP ANALYSIS
4. ⚡ SHIFT-LEFT RECOMMENDATIONS
5. 📈 TEST PYRAMID ANALYSIS
6. 🎯 PRIORITIZED ACTION PLAN

---

1. AC Coverage Matrix

============================================================================================
📊 ACCEPTANCE CRITERIA COVERAGE MATRIX
============================================================================================

| AC # | Description                         | Manual TC | Unit Tests | Integration | UI Auto | Status   |
|------|-------------------------------------|-----------|------------|-------------|---------|----------|
| AC-1 | Field validation                    | 5         | 4          | 1           | 2       | ✅ 85%   |
| AC-2 | Character limits                    | 3         | 3          | 0           | 1       | ✅ 90%   |
| AC-3 | Dropdown functionality              | 4         | 0          | 2           | 3       | 🟡 65%   |
| AC-7 | Console compatibility               | 2         | 0          | 0           | 2       | ❌ 40%   |

Legend: ✅ Good Coverage (>75%) | 🟡 Moderate Coverage (50-75%) | ❌ Poor Coverage (<50%)

============================================================================================

2. Manual TC Automation Coverage

============================================================================================
📋 MANUAL TEST CASE AUTOMATION COVERAGE
============================================================================================

| Manual TC ID        | Scenario Type | Technique | Unit | Integration | UI Auto | Recommendation            |
|---------------------|---------------|-----------|------|-------------|---------|---------------------------|
| PS-12345-AC1-TC010  | Positive      | EP        | ✅   | ✅          | ✅      | ✅ Well covered           |
| PS-12345-AC1-TC020  | Negative      | BVA       | ✅   | ❌          | ❌      | ⚠️ Add integration test   |
| PS-12345-AC2-TC010  | Positive      | Use Case  | ❌   | ❌          | ✅      | 🔴 Move to unit test      |
| PS-12345-AC2-TC020  | Boundary      | BVA       | ✅   | ❌          | ❌      | 🟢 Good — unit sufficient |

Technique Key: EP=Equivalence Partitioning | BVA=Boundary Value Analysis | Decision=Decision Table

Recommendation Legend:
✅ No Action Needed | 🟢 Good Level | ⚠️ Medium Priority (fill gap) | 🔴 High Priority (shift left)

============================================================================================

3. Coverage Gap Analysis Format

Structure gaps by priority level:

============================================================================================
🔍 COVERAGE GAPS IDENTIFIED
============================================================================================

🔴 CRITICAL GAPS (High Priority):
--------------------------------------------------------------------------------------------
1. AC-7: [Description]
   Manual TCs: [Affected TC IDs]
   Current Coverage: [What exists today]
   Missing: [Specific test types needed]
   Impact: [Risk if gap not closed]
   Recommendation: [Specific action — number of tests to add, file locations]

🟡 MODERATE GAPS (Medium Priority):
--------------------------------------------------------------------------------------------
2. AC-3: [Description]
   [Same structure as above]

🟢 MINOR GAPS (Low Priority):
--------------------------------------------------------------------------------------------
3. AC-2: [Description]
   [Same structure — consolidation/optimization opportunities]

============================================================================================

4. Shift-Left Recommendations

Target Test Distribution

Level	Current Target	Ideal Target	Notes
Unit Tests	60–70%	Business logic, validation, error messages
Integration Tests	20–30%	API responses, service calls, data transforms
UI Automation	10–15%	Critical happy paths only
Manual Only	5–10%	Exploratory, accessibility, UX-specific

Shift Priority Format

============================================================================================
⚡ SHIFT-LEFT RECOMMENDATIONS
============================================================================================

CURRENT TEST DISTRIBUTION:
Unit Tests: XX (XX%)  ← Should be 60-70%
Integration: XX (XX%) ← Should be 20-30%
UI Automation: XX (XX%) ← Should be 10-15%
Manual Only: XX (XX%) ← Should be 5-10%

🔴 HIGH PRIORITY — Move to Unit Tests:
--------------------------------------------------------------------------------------------
1. [Manual TC ID]: [Test title]
   Current: UI automation test
   Reason: [Why this is a unit test concern]
   Benefit: [Execution speed gain, reliability improvement]
   Effort: [Low/Medium/High (~X hours)]
   Suggested Implementation:
     [Brief code skeleton or test description]

🟡 MEDIUM PRIORITY — Move to Integration Tests:
--------------------------------------------------------------------------------------------
[Same structure]

🟢 LOW PRIORITY — Consolidate UI Tests:
--------------------------------------------------------------------------------------------
[Same structure]

ESTIMATED SAVINGS:
Execution Time Reduction: ~XX minutes per run
Test Reliability Increase: ~XX%
Maintenance Effort: -XX%
Total Implementation Cost: ~XX hours
ROI Timeline: X-X months

============================================================================================

5. Test Pyramid Analysis

============================================================================================
📈 TEST PYRAMID HEALTH CHECK
============================================================================================

CURRENT STATE:                          TARGET STATE:

    Manual (XX%)                           Manual (5%)
   ▼▼▼▼▼▼▼▼▼▼                            ▼▼

   UI Auto (XX%)                          UI Auto (13%)
  ▼▼▼▼▼▼▼▼▼▼▼▼                          ▼▼▼▼▼▼

  Integration (XX%)                       Integration (22%)
 ▼▼▼▼▼▼▼                               ▼▼▼▼▼▼▼▼▼▼▼

 Unit Tests (XX%)                        Unit Tests (65%)
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼                    ▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼

ISSUES IDENTIFIED:
❌ [Issue — e.g., "Inverted Pyramid: Too many tests at UI level"]
⚠️ [Warning — e.g., "Integration gap: API interactions not tested in isolation"]

RECOMMENDED ACTIONS:
1. [Specific action with test count and file targets]
2. [Specific action]

============================================================================================

6. Prioritized Action Plan

Structure as three phases:

============================================================================================
🎯 PRIORITIZED ACTION PLAN
============================================================================================

PHASE 1: Quick Wins (1–2 weeks, ~20 hours effort)
--------------------------------------------------------------------------------------------
1. ✅ [Action title]
   Tests to add/change: X
   Target files: [paths]
   Expected benefit: [specific metric improvement]

PHASE 2: Strategic Improvements (2–4 weeks, ~30 hours effort)
--------------------------------------------------------------------------------------------
[Same structure]

PHASE 3: Coverage Completion (4–6 weeks, ~20 hours effort)
--------------------------------------------------------------------------------------------
[Same structure]

EXPECTED OUTCOMES:
--------------------------------------------------------------------------------------------
✅ Test pyramid optimized to industry best practices
✅ [Specific improvement metric]
✅ [Specific improvement metric]

============================================================================================

Review Coverage Matrix (For Test Case Reviewer)

When used in review context, the AC coverage matrix format is:

| AC #  | Description          | Test Cases | Positive | Negative | Boundary | Status      |
|-------|----------------------|------------|----------|----------|----------|-------------|
| AC-1  | [Description]        | 5          | 3        | 1        | 1        | ✅ Complete |
| AC-2  | [Description]        | 3          | 2        | 1        | 0        | 🟡 Partial  |
| AC-3  | [Description]        | 0          | 0        | 0        | 0        | ❌ Missing  |