-
Notifications
You must be signed in to change notification settings - Fork 554
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
#16 Uncovered source files. #252
Conversation
…ee zero coverage reports for files that have no test defined.
Thanks. Yeah, it would be nice to have a setup that verifies this in a cuke feature so I don't accidentally break this in the future. Not sure whether we'd need a separate faked project, but probably the current one would work just fine by just running the code instead of a specific test suite. |
@jwickard, thanks for this, I just tested out your branch on my project and it's very close to what I was trying to do. Maybe another way to test it would be to dynamically create the "uncovered" file in the test? |
689480e
to
ec43ea9
Compare
You up for updating this? |
c7c5ad5
to
4c39fa3
Compare
Ping! I’m trying to put together a new release. Please update if you want this feature included. |
fd640fa
to
739cf4d
Compare
@jwickard would you be up to rebasing this? |
Replaced by #422. |
implements Feature from issue #16
Off by default, but if someone wants it, they can just set show_uncovered_files to true in the config block.
Why aren't there tests?
I tried to write a few features to demonstrate the functionality but the way the test harness run it touches the uncovered source file and shows up in the coverage data. So basically when I run the tests I can't recreate the issue.
If it's a big deal maybe I can spend some time in the future trying to work that up.