News for hackers. Stuff that matters.
Re:The tragedy of 100% code coverage (2016) by detaro on Tuesday May 09, 2017 @07:26AM (#14299066)
Your comparison source could be running on a different platform, or be slower, or ... and thus not be a drop-in replacement. (E.g. in the example of a broken floating-point unit, compare the results with a software emulation)
Re:The tragedy of 100% code coverage (2016) by StavrosK on Tuesday May 09, 2017 @08:09AM (#14299294)
Hmm, true, it may have been a different platform/slower, thanks. It can't have been hardware/software, as the GP said they were testing a library (which implies software).