Re:The tragedy of 100% code coverage (2016)
by MereInterest on Tuesday May 09, 2017 @07:29AM
(#14299078)
How would automated mutation testing handle the case of accidentally causing infinite loops, or invoking undefined behavior?
[ Parent
| on HN ]
Re:The tragedy of 100% code coverage (2016)
by rjdavis3 on Tuesday May 09, 2017 @09:45AM
(#14299903)
I use pitest to run mutation coverage on most of my Java code bases. pitest implements a timeout to check for infinite loops introduced by changing the code.
Re:The tragedy of 100% code coverage (2016)
by computerex on Tuesday May 09, 2017 @11:45AM
(#14300982)
Pitest has solved the halting problem?
In the real world, you can't wait five minutes for the server to return a response. If the server returns the correct response after ten minutes, it's still wrong, unless the programmer has explicitly acknowledged that the procedure in question is a long-running procedure and has lengthened (but not eliminated) the time-out accordingly.
The halting problem is an irrelevant, Ivory-tower distraction in production code.