show your output, we can only guess at the problem otherwise
that said, you probably want to use always_run: true and pass_filenames: false -- also your entry is bogus, no need to wrap things in bash, just call the executable directly. Putting all that together:
- repo: local
hooks:
- id: pytest-check
name: pytest-check
entry: pytest
language: system
pass_filenames: false
always_run: true
disclaimer: I am the author of pre-commit
Answer from anthony sottile on Stack Overflowpython - Running pytest as a pre-commit hook - no such file or directory issue - Stack Overflow
pre-commit hook fails but pytest runs fine if called directly
pytest doesn't locate tests
I built a pre-commit hook that enforces code coverage thresholds
Videos
show your output, we can only guess at the problem otherwise
that said, you probably want to use always_run: true and pass_filenames: false -- also your entry is bogus, no need to wrap things in bash, just call the executable directly. Putting all that together:
- repo: local
hooks:
- id: pytest-check
name: pytest-check
entry: pytest
language: system
pass_filenames: false
always_run: true
disclaimer: I am the author of pre-commit
If you are running various kinds of files through pre-commit or using hooks before you commit, you'll need to add another parameter to the .pre-commit-config.yaml file or it will fail with an exit code of 5 (no tests ran):
- repo: local
hooks:
- id: pytest-check
name: pytest-check
stages: [commit]
types: [python]
entry: pytest
language: system
pass_filenames: false
always_run: true
The addition of the types parameter will allow you to pass pre-commit even if no tests ran or there are no Python files.
What My Project Does
coverage-pre-commit is a Python pre-commit hook that automatically runs your tests with coverage analysis and fails commits that don't meet your specified threshold. It prevents code with insufficient test coverage from even making it to your repository, letting you catch coverage issues earlier than CI pipelines.
The hook integrates directly with the popular pre-commit framework and provides a simple command-line interface with customizable options.
Target Audience
This tool is designed for Python developers who:
-
Take test coverage seriously in production code
-
Use pre-commit hooks in their workflow
-
Want to enforce consistent coverage standards across their team
-
Need flexibility with different testing frameworks
It's production-ready and stable, with a focus on reliability and ease of integration into existing projects.
Comparison with Alternatives
-
https://github.com/Weird-Sheep-Labs/coverage-pre-commit: doesn't fail commits that don't pass a coverage threshold, what it does should probably be part of a CI pipeline.
Unlike custom scripts that you might write yourself, coverage-pre-commit:
-
Works immediately without boilerplate
-
Handles dependency management automatically
-
Supports multiple test providers with a unified interface
-
Is maintained and updated regularly
Key Features:
-
Works with unittest and pytest out of the box (with plans to add more frameworks)
-
Configurable threshold - set your own standards (default: 80%)
-
Automatic dependency management - installs what it needs
-
Customizable test commands - use your own if needed
-
Super easy setup - just add it to your pre-commit config
How to set it up:
Add this to your .pre-commit-config.yaml:
- repo: https://github.com/gtkacz/coverage-pre-commit
rev: v0.1.1 # Latest version
hooks:
- id: coverage-pre-commit
args: [--fail-under=95] # If you want to set your own thresholdMore examples:
Using pytest:
- repo: https://github.com/gtkacz/coverage-pre-commit
rev: v0.1.1
hooks:
- id: coverage-pre-commit
args: [--provider=pytest, --extra-dependencies=pytest-xdist]Custom command:
- repo: https://github.com/gtkacz/coverage-pre-commit
rev: v0.1.1
hooks:
- id: coverage-pre-commit
args: [--command="coverage run --branch manage.py test"]Any feedback, bug reports, or feature requests are always welcome! You can find the project on GitHub.
What do you all think? Any features you'd like to see added?