Repository navigation
Add code coverage metrics and reporting #45
Description
Problem
No code coverage reports or targets configured for Rust, Python, or TypeScript. Hard to track if new code maintains test quality.
Action
- Add
cargo-llvm-covorcargo-tarpaulinfor Rust coverage - Add
pytest-covfor Python coverage - Integrate coverage reports into CI (e.g. Codecov or Coveralls)
- Consider setting minimum coverage thresholds for PRs
Generated from production readiness audit
Activity
jsam commentedon Aug 21, 2026
Partial: Rust coverage has been in CI for a while (Coverage job runs make coverage via cargo-llvm-cov and uploads the report on every PR). Still open: Python SDK coverage (pytest-cov), TypeScript coverage, and any minimum-threshold gating. Also note the coverage job currently measures only the root crate - the workspace now has gateway and ontology-client crates (from #105) that the coverage run should include.
jsam commentedon Oct 1, 2026
Rust tarpaulin coverage exists. Remaining: run with --workspace (gateway, ontology-client), pytest-cov and vitest coverage, a baseline, then fail-under. The --workspace part lands in wp-ci-gate.
jsam commentedon Oct 4, 2026
Moved to Later / deferred. Code coverage reporting: deferred.
The neurosymbolic decision layer plan narrows the roadmap to two milestones: Engine production readiness (current focus), then Gateway neural integration (Jev, CLM, Laya) (#266). This issue stays open and can be pulled back in. Tracker: #199.
jsam commentedon Oct 10, 2026
Rust coverage runs through tarpaulin in make coverage and CI, but only for the root crate and without a baseline or threshold. The Python and TypeScript parts left with the SDKs removed in https://github.com/inputlayer/inputlayer-symbolic/pull/14. Remaining work continues in https://github.com/inputlayer/inputlayer-symbolic/issues/124.