Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Even if `tests-dir` is specified, pytest still collects tests on all the repository
See original GitHub issueLong story short, I have a repository which is quite packed, including sub-directory that have their own tests sub-sub-directory.
When I run mutmut run --tests-dir tests/unit/, the first step still runs python -m pytest -x, which fails on my use case (because of the tests sub-sub-directories which should not be executed).
I would have expected mutmut to run python -m pytest -x tests/unit/ instead.
Is there a point to run pytest on the whole repository or is it an oversight?
(version 1.6.0)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Glad to hear it!
If you have social media followers or a blog spread the word! 😃
That’s what I did, but I was wondering if it was the intended behaviour or if it is was a bug. Just letting you know in case of 😃