Re:Greatest: C unit testing library in one file
by silentbicycle on Wednesday January 08, 2014 @01:35AM
(#7022090)
Knowing that a change broke a specific set of tests tells you a lot more than knowing it broke the first one of them that happened to run.
If I'm using fuzzing to run thousands of tests, and all the ones whose seed led to the same specific bit pattern are failing, that's particularly useful information. I found a particularly subtle bug in heatshrink (https://github.com/atomicobject/heatshrink) that way, but a single failing test would have looked like noise.
Though I like your style, very simple, and simple is good. The state is binary, tests are passing or they are not. Unfortunately in this particular reality the added complexity of knowing all broken tests can prove very useful.