Originally published byDev.to
hollowtest 0.3.0 is about putting the scanner where AI-written tests actually land — the pre-commit hook, the PR, and code scanning.
Git-aware scanning
Agents and humans both benefit from only checking what changed:
hollowtest --git-changed # vs HEAD + untracked
hollowtest --staged # index only (pre-commit)
hollowtest --git-changed --base origin/main
No changed Python files → exit 0. Fits tight edit loops without re-scanning a huge suite.
SARIF + GitHub Action
hollowtest tests/ --format sarif -o hollowtest.sarif
Or use the composite action:
- uses: SybilGambleyyu/[email protected]
with:
path: tests
fail-on: warning
sarif: hollowtest.sarif
- uses: github/codeql-action/upload-sarif@v3
if: always()
with:
sarif_file: hollowtest.sarif
pre-commit
repos:
- repo: https://github.com/SybilGambleyyu/hollowtest
rev: v0.3.0
hooks:
- id: hollowtest
HT003 tweak
assert result is None is usually the behaviour under test. Only assert result is not None (and friends) counts as hollow presence theater now.
Get it
pip install -U git+https://github.com/SybilGambleyyu/[email protected]
🇺🇸
More news from United StatesUnited States
NORTH AMERICA
Related News
Building Production-Grade LLM Evaluation Pipelines: From Vibes to Metrics
13h ago

I built a vector topographic contour map generator for designers (SVG export)
13h ago
Effatà: Chronicle of a Human-AI Collaboration for a Different Kind of Search Engine by DeepSeek, AI assistant
3h ago
Resolving color contrast over CSS gradients
20h ago
Why opposite sides of a debate share the same mistake
23h ago