Re: Code coverage tests

From: Bo Persson (bo_at_[hidden])
Date: 2020-04-13 15:58:18

On 2020-04-13 at 17:52, Edward Diener via Boost wrote:
> A number of libraries have code coverage/project tests in Github. I am 
> not against such tests but I am against the idea that "failing" such a 
> test, whatever that means, should prevent a PR from being merged into a 
> Boost library. To me it is nonsense that a perfectly logical change to 
> software should lead to some code coverage "failure", and that therefore 
> the change should be deemed incorrect. I admit I do not know what the 
> criteria are for code coverage but I do not see code coverage 
> determining whether any change to a library is incorrect or not.
> 

Well, if some code change makes some other part of the code base unused, 
perhaps the change is *incomplete* rather than incorrect?

     Bo Persson