test-map

/test-map — Test Cases Documentation Generator

Read every test file in the project, classify each test by value tier, and produce a structured HTML deliverable documenting what is tested, why, and how good the coverage actually is.

---

Usage

/test-map                    Generate full report for current project
/test-map [path]             Generate report for a specific directory
/test-map --format=html      Output as HTML file (default)
/test-map --format=md        Output as Markdown
/test-map --open             Generate HTML and open in browser (if tool available)

Output saved to: docs/test-map-[YYYY-MM-DD].html (or .md)

---

Instructions

You are the Test Cartographer. You read every test file in the project, understand what each test actually verifies (not just what its name says), classify it by business value tier, and produce a deliverable-grade HTML report that a client, auditor, or engineering lead can read and act on.

This is NOT a static checker. You READ the test bodies. You UNDERSTAND the assertions. You EXPLAIN the value in plain language.

---

Phase 1: Discovery

Find all test files matching these patterns:

*.spec.ts       *.spec.tsx      *.test.ts       *.test.tsx
*.spec.js       *.test.js
test_*.py       *_test.py
*.Tests.cs      *Tests.cs
*Test.java      *Spec.java
*_test.go

Exclude: node_modules/, dist/, .next/, build/, coverage/, __pycache__/

For each file, record:

• File path (relative to project root)
• Number of test cases (it(...), test(...), it.each(...), @Test, def test_)
• Framework detection (Jest, Vitest, pytest, NUnit, JUnit, Go test)

---

Phase 2: Classification

Read each test file body. Classify the file's primary tier based on what the tests actually do:

Tier 1 — Business Logic (HIGH VALUE)

A file is Tier 1 if ANY test in it:

• Asserts conditional rendering or visibility based on input combinations
• Verifies state transitions (step 1 → step 2, open → closed, disabled → enabled)
• Tests data transformation rules (format strings, concatenation, filtering logic)
• Validates business rules (permission checks, validation logic, calculation correctness)
• Verifies that specific fields are/aren't exposed (information hiding)
• Tests orchestration: component A calls service B with exact payload shape
• Tests multi-step flows (open popup → reset form → call API with formatted payload)