name-tests-test isn't Django-friendly
See original GitHub issuehttps://docs.djangoproject.com/en/1.7/topics/testing/advanced/#using-different-testing-frameworks
Django’s built-in test runner defaults to searching for test*.py
. It would be nice if name-tests-test
either allowed both the test*.py
and *_test.py
patterns or if there was a separate hook for the Django-style test naming pattern.
I’d be happy to submit a PR for the preferred solution/implementation.
Issue Analytics
- State:
- Created 9 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Some modelling advice - Using Django
A test is exclusively in a single category, and whilst it isn't the case today, there is no reason why a Category cannot...
Read more >Supported hooks - pre-commit
name-tests -test - verifies that test files are named correctly. no-commit-to-branch - don't commit to branch; requirements-txt-fixer - sorts entries in ...
Read more >Why Most Unit Testing is Waste [pdf] - Hacker News
Throwing away unit tests is like saying "This ship has been sailing for years and has never sunk - let's throw away the...
Read more >Save the logs generated during a pytest run as a job artifact ...
We will retrieve the module, class and function name from the request object. log_path = Path("tests") / "logs" : loguru accepts File-like ...
Read more >Mocking Context Managers in Python - Jeremy Satterfield
testing. I've often found Python's context managers to be pretty useful. They make a nice interface that can handle starting and ending of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
that output makes sense if you’re using the
--django
flaganyway I resolved the problem that I have through
pytest.ini
thank you for your fast reply @asottile