DUnit - class MyTest { mixin TestMixin; void testMethod1() {} void testMethod2() {}}

[Jacob Carlborg]

On 2012-02-19 19:18, Juan Manuel Cabo wrote:
>
>> Interesting, congrats. A common question that will come up is
>> comparing, contrasting, and integrating your work with the existing
>> unittest language feature. You may want to address these issues
>> directly in the documentation.
>
> Thanks!! I'll put it in the doc (and also clean up my crude
> documentation formatting). I plan to keep improving dunit too.

You can can write the README file using markdown, github understands 
that format.

> * DUnit provides a style of unit testing popularized in the OOP crowd
> which begun with sUnit by Kent Beck (smalltalk), later jUnit by Kent Beck
> and Erich Gamma (java), and then also NUnit for .NET (there also exists
> too FlexUnit for Flex, FireUnit for Javascript, CppUnit for C++ etc., but
> those deviate a little from the originals).
> So DUnit brings D to the familiy of languages that support certain
> testing idioms familiar to many OOP developers. (tests fixtures (grouped by
> classes), with common initialization, green bars ;-), decoupled test
> runners,
> convenience assert functions, etc.
> (I'm thinking of writing a quick DWT GUI test runner too

Cool.

> # (OFFTOPIC: I made a patched DWT that works in linux 64bits (by fixing
> a few bugs and commenting out some impossible XPCOM code
> and I'll try to sync to Jacob Carlborg's github repo
> when I have more time; and fixed missing 'double vars=0' inits instead of
> NaN that produced slowdowns and prevented certain drawing functions
> from working in the Graphics Context)).
> --jm

Pull requests are welcome.

-- 
/Jacob Carlborg