Re:The tragedy of 100% code coverage (2016)
by anamexis on Tuesday May 09, 2017 @12:52AM
(#14297810)
It seems to me that such a "perfect" testing process would basically amount to declarative programming.
Re:The tragedy of 100% code coverage (2016)
by TeMPOraL on Tuesday May 09, 2017 @04:27AM
(#14298489)
Indeed it is; a perfect test is equivalent to the code being tested.
Well...SQL is declarative, and we still see "Select * from Users"
Re:The tragedy of 100% code coverage (2016)
by ZeroGravitas on Tuesday May 09, 2017 @08:30AM
(#14299411)
Several other people are complaining about 100% coverage sometimes being misleading. One way to test your test is to randomly modify your code e.g. swapping a greater than for a less than. If your tests still pass, then they obviously missed this change in behaviour.
This is known as mutation testing.
https://en.wikipedia.org/wiki/Mutation_testing
I've tried it a few times, I generally found it too slow to be an everyday part of my routine, but interesting tool to have in your belt for e.g. evaluating test in a codebase you didn't write yourself.
Re:The tragedy of 100% code coverage (2016)
by rjdavis3 on Tuesday May 09, 2017 @09:54AM
(#14299991)
Have you ever tried it with one of the automated tools? I use Pitest extensively to mutate my Java code bases and found it is not too much slower then regular line and branch code coverage tools when you use a history file so only diffs are needed. The trade off of a few more seconds of build time is worth the benefit of the coverage report and being able to fail the build if coverage drops too low for me.
Just so we're clear, my username was not inspired by this scheme.