gaia-test-gap-analysis

Test gap analysis identifies coverage gaps by mapping test plan entries to story acceptance criteria and flagging untested items. It scans test artifacts and implementation artifacts to compute coverage metrics and surface untested areas for QA planning.

A FR-223 compliant report is a structured document featuring an Executive Summary, Per-Module Coverage, Per-Story Detail, and a Gap Table. It maps traceability between test plans and acceptance criteria to enforce quality verification standards.

Generate a traceability report by scanning test-plan.md to map test cases to story keys. The analysis then extracts acceptance criteria from implementation artifacts to produce a structured gap report with actionable remediation nudges.

Yes, test gap analysis operates in two modes: coverage mode as the default and verification mode. Both modes use test artifacts and generated test data to produce a compliant report identifying untested acceptance criteria.

Test gap analysis enforces read-only fork context and time-bound execution under 60 seconds. These constraints ensure safe, rapid scanning of test plans and implementation artifacts without modifying the repository.

Use a gap analysis tool when you need to automatically extract acceptance criteria from multiple story files and compute per-module coverage metrics. It provides structured remediation nudges that manual cross-referencing cannot efficiently scale to produce.