Robert Fraser wrote:
> Robert Fraser wrote:
>> Christopher Wright wrote:
>>> Have you started such a plugin? If so, I'd love to help out. If not, any
>>> suggestions on where to get started?
>>
>> Nope, it's on my *long* TODO list. I'm not even sure how to go about making it a CC plugin, I'd have to check how the JUnit plugin works. It might end up being an Ant task with some sort of listener/presentation component in CC.
> 
> I took a look into this & it appears that the best solution is to create a tool that outputs unit test result XML in the same format as JUnit. CC can just pick that up & display it as JUnit tests. For full CC integration, adding another builder (such as a DSSS builder) would be a good idea, though.

I came to the same conclusion, though I didn't find an adequate description of the JUnit schema. I'll have to snag some output instead, I guess.

> That said, it would be a cool idea to have a unified, configurable D "testing framework" that could run both DUnit tests and built-in unittest { } blocks with a plugable reporter interface for output (i.e. a JUnit-compatible XML for CC plugability, a pretty Web 2.0-ish page for Zen staring sessions, etc.)

Yep, but that's too much work for me to do.