The scan job now runs both suites with coverage before scanning: pytest --cov (pyproject.toml: scripts/ without its tests, relative paths, coverage.xml) and `npm run test:coverage` (vite.config.ts: v8, lcov with projectRoot "..", so paths start web/). sonar-project.properties names both reports and drops sonar.coverage.exclusions. requirements-test.txt gains pytest-cov 7.1.0 and coverage 7.16.2 with every file's hash (uv pip compile --universal --generate-hashes --python-version 3.15; the existing pins are unchanged). web gains @vitest/coverage-v8 5.0.5, matching vitest; none of its packages has an install script. Coverage stays off for a plain `npm test`. The token check is its own job, so the scan steps no longer each repeat the condition; the workflow grants nothing at the top and the scan job contents: read. `npm run build:admin` replaces the bare `svelte-kit sync`: it syncs too, and writes the admin bundle the Worker's tests load. Locally: 576 vitest tests at 58.35% of lines, 299 pytest tests at 57.7%. Against main's new-code lines (SonarCloud's isNew), the reports cover 92 of 114 coverable lines, 80.7%: the 80% gate is borderline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15 lines
489 B
TOML
15 lines
489 B
TOML
# Tooling configuration only - this repo is not a pip-installable package.
|
|
|
|
[tool.vulture]
|
|
paths = ["scripts"]
|
|
# pytest collects test_* functions and fixtures by name; vulture cannot see that.
|
|
exclude = ["scripts/tests/"]
|
|
min_confidence = 80
|
|
|
|
# pytest --cov (sonarcloud.yml): the pipeline's code, not the tests that drive
|
|
# it, with paths relative to the repository root, where the scan reads them.
|
|
[tool.coverage.run]
|
|
source = ["scripts"]
|
|
omit = ["scripts/tests/*"]
|
|
relative_files = true
|