Closed stoffeastrom closed 6 years ago
@stoffeastrom good find, I will take a look and see if I can make a failing test for this and then add the fix it to the 1.3.1 release!
But yes it should show partial as one of the AND branches seems to not have been hit (if I read the screenshot correctly)
I have also never seen any partial coverage highlights, don't know why.
@villelahdenvuo can you see the partial coverage in the example project if you run that? if you are using xml based coverage files there isnt partial support yet as the xml parse module, I am using, doesnt have the functionality present.
@stoffeastrom looked into this issue and added some more advanced test cases to better mimic real world code examples, I think this issue stems from the fact that there is an unexplored else path that is causing the partial coverage in your original picture. You can see below that when I open the coverage report you can see that there is an E icon (represents an else path not traveled). going to close this one for now as imo the missing else shouldnt make a partial coverage indicator.
Looking at coveralls
Should it display partial coverage or full for this use case?