Continuous Integration

[Jason House]

Christopher Wright wrote:

> Jason House wrote:
>> I'm sensitive to per-unittest code-writing overhead, but already have
>> some in my code. If DUnit offers comparable overhead, and enhanced
>> functionality, I'll switch.
> 
> DUnit uses test fixture classes, so it probably won't suit you at
> present. I'll look into a method with less overhead.

Hmmm... maybe :(

Would this be possible?

unittest{
  mixin DUnitTest!("My test name",
  {
    ...// my code
  });
}


My limit is probably something near:

unittest{
  mixin startTest!("My test name");
  try{
    ... // my code
  catch{
    mixin catchTest;
  }
}


I'd like to stay with the D style of unit tests.  Maybe I should check what
enhancement requests are in there.  It'd be nice to be able to hook in a
unit test handler...