Pretty sure I addressed all remaining comments.

Atila

I'm looking forward to this addition. Good job.

Does unit-threaded (branch: experimental) contain the same as the pull request for std.experimental.testing?
I've only read about it (PR+forum) so far and dying of curiosity to test it out for real.

Questions.
Does it contain a way to plugin ones own "result writer"?
Remove/replace the current "console writer"?

//Joakim

On Monday, 27 July 2015 at 14:59:48 UTC, Joakim Brännström wrote:
> I'm looking forward to this addition. Good job.
>
> Does unit-threaded (branch: experimental) contain the same as the pull request for std.experimental.testing?

Pretty much.

> I've only read about it (PR+forum) so far and dying of curiosity to test it out for real.

You can:

1) Use unit-threaded with dub and a "unittest" configuration. Most of the PR changes were cosmetic, it's basically the same thing.
2) Clone my phobos fork and use std.experimental.testing
3) Clone unit-threaded and use the "experimental" branch

Just beware that with 2.067 there's a crashing bug if you use it with "unittest" blocks. It's been fixed in the meanwhile, but if you don't use dmd HEAD then stick to test functions (which don't exist anymore in std.experimental.testing since there's no need for them anymore).

>
> Questions.
> Does it contain a way to plugin ones own "result writer"?

No, but it's a neat idea. I can see a demand for XML/HTML/JSON output for continuous integration.

Atila

I will do the review management