Austin Clements <amdragon at MIT.EDU> writes: > Previously, if a test script aborted (e.g., because it passed too few > arguments to a test function), the test driver loop would simply > continue on to the next test script and the final results would > declare that everything passed (except that the test count would look > suspiciously low, but maybe you just misremembered how many tests > there were).
Pushed, d
