[Issue 5283] Increase granularity of unit tests so that all unittest blocks in a module run even after another block fails

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=5283

--- Comment #2 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
(In reply to Dmitry Olshansky from comment #1)
> Jonathan, do you customizable test runner that D currently has still not
> addresses this? Including ready-made cutomizations such as unit-threaded and
> friends on dub.

Personally, I only ever use the built-in test runners, and I have no clue what
improvements have been made since I reported this (though I'm sure that the
behavior for the default test runner is the same). Based on what I've seen
Atila say about unit-threaded, I _think_ it's the case that he's able to use
__traits(getUnittests, ...) (or something like that anyway) to access each
unittest block directly and run it, in which case, presumably means that he can
make it run any combination of tests he wants, but I don't know. I'm fairly
certain that ___traits bit that he uses didn't exist when this was reported.

If other test runners can indeed run all of the tests in a module now, then
there really isn't any reason to leave this open, but the default test runner
has worked well enough for me that I haven't bothered to mess with others, so I
don't know what they can or can't do in this regard.

--