4 ms·

How would automated mutation testing handle the case of accidentally causing infinite loops, or invoking undefined behavior?

• rjdavis3 10y ago
  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. http://pitest.org/faq/ http://pitest.org/faq/
  • computerex 10y ago
    Pitest has solved the halting problem?
    • mcv 10y ago
      Timeouts are not a perfect solution to the halting problem, but usually good enough.
    • solatic 10y ago
      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.