Skip to content

Enforce the documented coverage threshold in CI #79

Closed

Description

@stefan-jansen

Problem

The repository configures coverage collection and documents a local report, but CI and release qualification run pytest without coverage and pyproject.toml defines no enforced minimum. The ecosystem standard requires the test lane to enforce its coverage threshold.

Acceptance criteria

  • pyproject.toml defines a conservative threshold supported by a fresh full-suite run.
  • Pull-request CI and release quality collect package coverage and fail below that threshold.
  • Contributor and agent verification commands match the enforced lane.
  • A focused test proves the configured threshold is active.
  • Ruff, ty, tests, resource warnings, strict docs, build, actionlint, and pre-commit pass.
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

    compatibility: noneNo known compatibility impactecosystemTracked by a shared ML4T ecosystem requirementpriority: normalNormal planned workstatus: acceptedAccepted for implementationtype: maintenanceInternal maintenance without user-visible behavior

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions