Component-Aware Test Gap Analysis

Test coverage gap analysis automatically scans your e2e test files to detect missing scenarios across components, platforms, and protocols. It analyzes networking, storage, and API tests against cloud platforms (AWS, Azure, GCP) and protocols (TCP, UDP, SCTP) to surface what's untested, then ranks gaps by priority and outputs HTML, JSON, and text reports.

Yes. The gap analyzer processes Go test files with Ginkgo framework to perform component-aware analysis. It detects the component type (networking, storage, or API), evaluates platform and protocol coverage, and identifies missing scenario coverage like error handling, upgrades, and RBAC across your e2e test suite.

The analyzer assesses coverage across cloud platforms (AWS, Azure, GCP, baremetal) and protocols (TCP, UDP, SCTP). It also evaluates service and storage characteristics alongside scenario coverage for error handling, upgrades, and RBAC to provide comprehensive platform and protocol gap prioritization.

Gap analysis produces three report formats—HTML, JSON, and plain-text—saved under .work/test-coverage/gaps/. Each report ranks identified gaps by priority (high, medium, low) to help teams focus testing efforts on the highest-impact coverage areas.

Yes. Gap analysis requires e2e or integration test files as input to analyze. Point the analyzer to your test directory or specific test file (for example, tests/e2e/networking_test.go) to detect component types, compute coverage scores, and generate gap reports.