Skip to content

Raise test coverage toward the CLDMV ~90% bar (currently ~33%) #3

Open

Description

@Shinrai

Surfaced during v4 onboarding (PR #2). The @cldmv/vitest-runner wiring + coverage reporting are now in place, but coverage is low because only a single pre-existing test file exists (tests/env-manager.test.mjs, 9 tests):

Metric Coverage
Lines 33.67%
Statements 33.79%
Functions 52.23%
Branches 25.89%

CLDMV libs aim for ~90%. Add unit/characterization tests covering the untested src/ paths — the env-manager logic and its platform-specific branches (posix vs win case-sensitivity, PATH handling, etc.). Non-urgent; tracking follow-up. Out of scope for the current fleet pass (which is v4 onboarding + dependency updates only).

Activity

  1. added
    staleNo activity for an extended period; will be auto-closed if it stays inactive
    on Oct 2, 2026
  2. cldmv-bot commented on Oct 2, 2026

    @cldmv-bot
    Contributor

    This issue has been inactive for 60 days. It will be auto-closed in 14 days if there is no further activity. Comment to keep it open, add the pinned label to exempt it permanently, or close it if it is no longer relevant.

  3. added
    pinnedLong-standing on purpose — exempt from the stale sweep, never auto-closed for inactivity
    and removed
    staleNo activity for an extended period; will be auto-closed if it stays inactive
    on Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    pinnedLong-standing on purpose — exempt from the stale sweep, never auto-closed for inactivity

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions