dunit r247

[Robert Fraser]

bearophile wrote:
> For me it's often better to keep tests very close to the things they test. It helps me spot and fix bugs faster, to avoid jumping across files, and when I quickly move a block of code (function, class, template, etc) when I reorganize the code it is less likely for me to lose its tests along the way. I think tests are a part of a function/class/template, just like its ddocs.

Well, you can always put the Dunit tests in the same module; this was 
just a suggestion.