-
-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.coveragerc doesn't support configuration of modules to be executed (like behave) #695
Comments
I don't understand the advantage of this? You'd still need to run "coverage run" somehow, so why not just leave the command line arguments there? |
Tools like flake8 or pyflakes support having their settings and arguments in setup.cfg or tox.ini, which lets people run only |
@nedbat |
@crd Of course I don't disagree with the idea of having a coverage config file. It's full of all sorts of useful things. I just hadn't personally seen the need for the rest of the "coverage run" command line to be in it, since it wouldn't save me a command line, just shorten it. The config file was originally created as a way to control options when running coverage within a test runner, where I couldn't parse command-line options to control coverage's behavior. |
Implemented in e575490. |
Thank you @nedbat, I realize you were iffy on the value of this line in .coveragerc but as someone on the hook for a few dozen prod apps it will be very nice to now be able to clone a project, Appreciate it! |
This was released as part of 5.0a4. |
Instead of specifying it all on the command line like this:
$ coverage run --omit "config/*,features/steps/*" -m behave features/local/
I would love to have something like this in my
.coveragerc
file:Omit works, but there's no way (as far as I can tell) to specify I want to execute
behave
against thefeatures/local
directory in my example.The text was updated successfully, but these errors were encountered: