I notice that dub test will stop at the first unit test failure.
Is this a feature or a bug?
Most Unit Test engines will run all the unit tests then give a
report such as:
10 files checked. 4 failed, 6 passed, with a list of files for
each.
In the old days, compilers would generate 300 errors, most of
which were useless.
Then Lightspeed C came out and stopped at the first error.
You were supposed to fix that one, then recompile to find any
others.
This made Lightspeed C much faster to compile as it didn't waste
time after finding the first error.
Should D developers fix one unit test at a time in a similar
manner?
