Skip to content
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

--no-skip-covered to negate --skip-covered #779

Closed
asottile opened this issue Feb 25, 2019 · 3 comments · Fixed by #932
Closed

--no-skip-covered to negate --skip-covered #779

asottile opened this issue Feb 25, 2019 · 3 comments · Fixed by #932
Labels
enhancement New feature or request fixed

Comments

@asottile
Copy link
Contributor

asottile commented Feb 25, 2019

Is your feature request related to a problem? Please describe.

For test run outputs, I set skip_covered = true in my .coveragerc (for example here). I do this to avoid the terminal spew of the 50+ 100% covered files.

However, for html outputs, I'd still like to have files included when running coverage html, even if they are 100% covered.

Describe the solution you'd like

I think the simplest solution would be to add --no-skip-covered options to the various coverage html / coverage report entrypoints which would override the --skip-covered option.

Describe alternatives you've considered

Not really seriously considered, but sed -i /skip_covered/d .coveragerc before running coverage html -- pretty haxy though ;)

Additional context

I'm mostly trying to target automated CI here, in particular azure pipelines coverage reporting

@asottile asottile added the enhancement New feature or request label Feb 25, 2019
@asottile
Copy link
Contributor Author

asottile commented Feb 14, 2020

@nedbat alternatively, should --skip-covered change the output for coverage html? it doesn't change the output of coverage xml for instance

@asottile
Copy link
Contributor Author

asottile commented Feb 14, 2020

@nedbat
Copy link
Owner

nedbat commented Jul 6, 2020

This is now released as part of coverage 5.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants