Skip to content

Conversation

Tinche
Copy link
Member

@Tinche Tinche commented Dec 2, 2024

No description provided.

@Tinche Tinche force-pushed the tin/branch-coverage branch 3 times, most recently from d9b9c5d to 261bdb2 Compare December 3, 2024 13:48
@salotz
Copy link

salotz commented Dec 3, 2024

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 Tinche force-pushed the tin/branch-coverage branch from 13cb051 to dd7e821 Compare December 3, 2024 16:02
@Tinche
Copy link
Member Author

Tinche commented Dec 3, 2024

I agree that it's annoying but it's also useful I think. Also doing it to have parity with attrs. ;)

@Tinche Tinche force-pushed the tin/branch-coverage branch from 81976ce to 97c446d Compare December 26, 2024 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants