Let's try branch coverage #607
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tinche
force-pushed
the
tin/branch-coverage
branch
from
9f818d5 to
53114bf
Compare
Tinche
force-pushed
the
tin/branch-coverage
branch
from
53114bf to
75a3094
Compare
Tinche
force-pushed
the
tin/branch-coverage
branch
from
d9b9c5d to
261bdb2
Compare
|
Branch coverage is so annoying. FWIW I use this pytest-checklist which I worked on which helps keep track of "unit" coverage. I.e. that every function has a test. Which IMO is of more primary importance than branch coverage. |
Tinche
force-pushed
the
tin/branch-coverage
branch
from
13cb051 to
dd7e821
Compare
|
I agree that it's annoying but it's also useful I think. Also doing it to have parity with attrs. ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.