Parallel execution of unittests

[Jacob Carlborg via Digitalmars-d]

On 2014-05-09 13:57, Dicebot wrote:

> This is redundant as D unittest blocks are associated with symbols they
> are placed next to.

I prefer to keep my tests in a separate directory.

> It introduces bunch of artificial annotations for something that can be
> taken care of by a single attribute as a side effect. Not KISS.

I just don't agree.

It's a bit hard to do in D, but in the Ruby version, for each "describe" 
block an anonymous class is created. Nested blocks inherits from the 
outer blocks. The "it" blocks are evaluated inside an instance of the 
closest "describe" block. This makes it very nice to setup data for the 
tests. You can have helper methods in the "describe" blocks, overriding 
methods in the outer blocks and so on, very convenient.

As a bonus, you can run the test with a special formatter. This will 
print all strings passed to the "describe" and "it" blocks in a 
structured way. Suddenly you can generate documentation of how you're 
system is supposed to work.

-- 
/Jacob Carlborg