ln-632-test-e2e-priority-auditor

E2E test coverage auditing validates that critical paths (Money, Security, Data with priority ≥20) and core journeys (priority 15–19) have adequate End-to-End tests. Run ln-632-test-e2e-priority-auditor against your test files and codebase structure to identify coverage gaps, flag wasteful tests, and receive a compliance score aligned with risk-based priority levels.

Risk-based priority auditing systematically maps your E2E tests against critical paths in Money, Security, and Data domains. The auditor applies priority thresholds (≥20 for critical, 15–19 for core journeys), flags underutilized or redundant tests, and outputs structured findings with recommended actions to close coverage gaps.

Yes. The auditor scores test usefulness and flags E2E tests that duplicate coverage or provide low value relative to risk. It returns guidance on which tests to consolidate or remove, helping optimize your test suite without sacrificing coverage of high-priority paths.

The audit generates coverage metrics for critical paths and core journeys, structured findings highlighting gaps and overuse, recommendations for remediation, and a final compliance score computed from the documented scoring algorithm. Results integrate with the ln-630 coordinator pipeline.

Run a priority audit when you need to validate that high-risk workflows in Money, Security, and Data have sufficient E2E coverage, after significant code changes that affect critical paths, or when test suite costs demand optimization. It ensures E2E tests are aligned with business-critical priorities.

The auditor requires the contextStore, your codebase structure, and test file lists as inputs. It applies these against risk-based priority definitions to map tests to critical paths and core journeys, then outputs coverage metrics and compliance scores.