News for hackers. Stuff that matters.
Re:How to add a million bugs to a program, and why you might... by gohrt on Thursday July 07, 2016 @08:04PM (#12052853)
You are overly harsh.

In all of testing, proving a negative is futile. But if this tool can create bugs that your bug-finder cannot find, and your real dev process is at all correlated to the bugs this tool creates, then this tool is a useful addition to the toolbox.

Re:How to add a million bugs to a program, and why you might... by Someone on Friday July 08, 2016 @03:30AM (#12054057)
But if this tool has detailed ideas about the kinds of bugs it can introduce. If so, the time spent on creating the tool to insert those types of bugs might have been better spent on creating specific test cases for those kinds of bug.

Alternatively, this randomly mutates programs, which means no time was lost thinking of what kinds of bugs to introduce. Then, I cannot see how the bugs introduced are representative of real-world ones. It just, as another commenter said, would be fuzzing your tests. Useful, but it doesn't tell you anything about the number of remaining bugs in your code.