Skip to content

Epic: 100% Framework/Sources coverage (measure, inventory, close gaps) #426

Description

@schatt

Summary

Product goal: 100% code coverage of Framework/Sources on executing test lanes (not tautologies, not orphan files).

#402 removed a never-wired suite. That does not close coverage; it only stopped counting fiction. Known L5 holes from that work are filed separately. This epic tracks measurement + remaining gaps so we do not treat those four issues as the whole product.

What “100%” means here

Already filed (do not duplicate)

Issue Gap
#422 MacOSOptimizationManager / MacOSPerformanceStrategy
#423 platformIOSHapticFeedback / IOSHapticStyle
#424 rest of PlatformIOSOptimizationsLayer5.swift
#425 docs-only L5 performance APIs (implement or delete docs)

Work in this epic

  1. Coverage reportingDevelopment/ROADMAP.md still has “Add code coverage reporting” unchecked. Produce a durable xccov (or equivalent) report from unit lanes; keep the full log (test-output-diagnostics).
  2. Inventory — uncovered files/functions, clustered by layer/module. First pass can be L5 (Framework/Sources/Layers/Layer5-Platform/ + platform L5 extensions), then L1–L4/L6.
  3. Spawn issues — one cluster per issue (like Add executing tests for MacOSOptimizationManager (L5 macOS) #422Implement or remove documented L5 performance APIs that do not exist #425). Do not dump the entire framework into one PR.
  4. Gate — decide whether release quality requires a coverage floor (today the release script is all tests pass, not a % gate). If we add a floor, put it in the release script, not a parallel undocumented check.

Out of scope for a single PR

Implementing 100% in one branch. This issue is the tracker.

References

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions