External lib unittests: they're killin me!

[Jens Mueller]

Jacob Carlborg wrote:
> On 2013-05-21 09:35, Jens Mueller wrote:
> 
> >It is possible and we shouldn't push functionality into the compiler
> >when the issue is solvable in a library.
> >https://github.com/jkm/dtest (shameless plug) has the command line
> >switch --include to specify which modules should be tested.
> 
> I'm using an rspec influenced library I wrote:
> 
> https://github.com/jacob-carlborg/dspec
> 
> Not very advanced. I still need a good way to run the tests. Now I'm
> just using a shell script. To see it in action, have a look here:
> 
> https://github.com/jacob-carlborg/orange/tree/master/tests
> 
> Yes, it does some operator overload abuse.

I have already seen it. I'm also looking for a more natural way to write
tests. dspec goes in that direction but I found its syntax
(describe("...") in {} and it("...") in {}) not convincing.
I was thinking about something like
a.should == 10;
or similar. But that has its own problems. Anyway writing/executing
unittests in D needs to become more fun.

Jens