didericis
632ab002ed
Adopt ADR 0004: stop chasing a single global coverage number and measure what matters instead. - Omit the genuinely-interactive `cli/init.py` shell (read_tty_line prompt loops) alongside the existing `cli/tui.py`, with a rationale comment in .coveragerc. Subprocess/backend orchestration is NOT omitted — it stays visible and is scored via the integration suite. - scripts/coverage.sh runs unit + integration under one coverage measurement (the policy's yardstick) and can report the critical security/logic core held to the >=90% target. - scripts/diff_coverage.py is a stdlib-only gate (no diff-cover dep): new/changed executable lines must be >=90% covered. This is the enforced regression guard; the global number is informational. - CI gains a `coverage` job: combined report + the diff-coverage gate. - Unit-test `cli/__init__.py` dispatch/exit-code mapping (it's logic, not I/O, so it earns tests rather than an omit). Combined unit+integration coverage now reports 83% global / 87% across the critical modules; per-module ratcheting toward 90% is the ongoing work this policy frames. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
19 lines
672 B
INI
19 lines
672 B
INI
[run]
|
|
branch = True
|
|
source = .
|
|
|
|
[report]
|
|
# Coverage policy: see docs/decisions/0004-coverage-policy.md.
|
|
#
|
|
# `omit` is reserved for genuinely interactive entry-point shells whose
|
|
# bodies are `read_tty_line()` / curses prompt loops — there is no
|
|
# behaviour to assert that a test wouldn't have to fake wholesale, so a
|
|
# test here would inflate the number without buying confidence. This is
|
|
# NOT a place to hide subprocess/backend orchestration: that code is
|
|
# security-relevant and is measured via the integration suite instead
|
|
# (run scripts/coverage.sh for the combined unit+integration number).
|
|
omit =
|
|
bot_bottle/cli/tui.py
|
|
bot_bottle/cli/init.py
|
|
tests/*
|