Skip to content

test-coverage: establish baseline coverage report for amplihack workspace #1735

Description

@rysweet

Parent tracking issue for goal improve-amplihack-test-coverage. We need an objective baseline before adding tests. Tasks: (a) Add cargo-llvm-cov or cargo-tarpaulin to CI tooling (prefer llvm-cov for speed and accuracy on the Rust workspace). (b) Produce a per-crate coverage report for the workspace as it stands on main. (c) Commit the baseline numbers to docs/testing/COVERAGE_BASELINE.md with date, commit SHA, and per-crate line+branch coverage. (d) Identify the 5 lowest-coverage crates that are also highest-risk (engineer_loop, ooda-brain, merge-authority, cognitive-memory, safe-update based on recent bug issues #1709/#1710/#1713/#1714/#1715/#1716). (e) File child issues, one per target crate, with a coverage-lift target (e.g., +20 percentage points) and a list of specific untested code paths. Do NOT write tests in this issue — this is purely measurement and planning.

Metadata

Metadata

Assignees

No one assigned

    Labels

    coverageTest coverage relatedtestingTest infrastructure / tooling / coverage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions