Test Structure Analysis

Test coverage analysis examines Go test files and source code statically to map which functions and files lack tests. This Skill parses test and source files using Go conventions, discovers test types (unit, integration, e2e), and generates reports showing untested areas without executing any tests.

Go test structure analysis identifies unit tests, integration tests, and end-to-end (e2e) tests using Go naming patterns and markers. It extracts test names, line ranges, and their target functions or packages to classify tests and map coverage comprehensively.

Yes, test structure analysis requires Python 3.8+ and a Go toolchain to parse files and run analysis. These tools enable discovery of Go test and source files, extraction of test and function metadata, and generation of coverage reports.

Test structure analysis generates three report formats: HTML for visual inspection, JSON for programmatic use, and text summaries. All reports are written to `.work/test-coverage/analyze/` and include details on test-to-source mappings and coverage gaps.

Run the analysis using `/test-coverage:analyze <path>` where path points to a Go test file, source file, or directory. The Skill discovers relevant files, parses them according to Go conventions, maps tests to sources, and outputs reports to `.work/test-coverage/analyze/`.

Functions without tests are flagged in the coverage reports as untested areas. Test structure analysis identifies files and functions lacking test coverage by comparing parsed source code against discovered tests, highlighting gaps for targeted test development.