unittests are really part of the build, not a special run

[Kagamin via Digitalmars-d]

On Wednesday, 1 April 2015 at 18:04:31 UTC, Ary Borenszweig wrote:
> However, when you have a big complex project you start having
> other needs:
> 1. Named unit-tests, so you can better find what failed
> 2. Better error messages for assertions
> 3. Better output to rerun failed tests
> 4. Setup and teardown hooks
> 5. Different outputs depending on use case

There are test frameworks for D: 
http://wiki.dlang.org/Libraries_and_Frameworks#Unit_Testing_Framework

> I'd say, deprecate "unittest" and write a good test library.

Test frameworks don't conflict with unittest blocks at all. They 
have different use cases.