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

100% coverage is not 100% #203

Closed
arcivanov opened this Issue Sep 20, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@arcivanov
Contributor

arcivanov commented Sep 20, 2015

With branch coverage being introduced there is a curious case of 100% code coverage possible without 100% branch coverage.

Whenever the following code is encountered:

    if a:
       pass

it's possible to achieve 100% coverage in the unit test by setting a to True, while never testing the behaviors when a is False. This needs to be rectified, possibly by adding a property specifying a separate branch coverage threshold and enforcing it separately from and in addition to line coverage.

arcivanov added a commit to arcivanov/pybuilder that referenced this issue Sep 21, 2015

arcivanov added a commit to arcivanov/pybuilder that referenced this issue Sep 23, 2015

@arcivanov arcivanov modified the milestone: v0.11.2 Sep 23, 2015

arcivanov added a commit to arcivanov/pybuilder that referenced this issue Sep 23, 2015

arcivanov added a commit to arcivanov/pybuilder that referenced this issue Sep 24, 2015

@arcivanov arcivanov closed this in #207 Sep 24, 2015

@arcivanov arcivanov removed the in progress label Sep 24, 2015

arcivanov added a commit that referenced this issue Sep 24, 2015

@arcivanov arcivanov referenced this issue Sep 24, 2015

Open

Catchup on documentation #199

0 of 15 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment