From: Mark Slater <lists@...>
Date: 2007-08-10T03:19:14+09:00
Subject: Re: HTML test output?

Well I've been searching, and unfortunately the best solution that  
used to exist (test-report) is gone, and I'm not comfortable tying  
our tests to software that doesn't exist anymore. Other solutions  
seem to be written for use with specific libraries (RSpec for  
example) and I don't want to introduce extra dependencies when all I  
need is a different logger.

So I've looked into writing my own; certainly the Console::TestRunner  
class isn't hard to understand and extend. The problem I've run into  
is that the rake TestTask only has the options attribute available to  
specify the test runner (t.options = "--runner=gtk", for example) and  
the list of available runners is baked into the Autorunners class. I  
haven't been able to add my custom runner to the list via the rake  
file because rake invokes a new process to run the tests (which is  
why the runner needs to be specified command-line-option-style).

At this point I'm looking at submitting a patch to Test::Unit with  
the new test runner that I make. I have to say though, with a  
language as dynamic as Ruby is, I'm surprised that the only *clean*  
way of adding a new test runner is to add it to the Test::Unit  
source; maybe I'm still too new though.

If I'm missing something, please let me know.

Mark

On Aug 9, 2007, at 12:38 AM, Jano Svitok wrote:

> On 8/8/07, Mark Slater <lists@humanesoftware.com> wrote:
>> Well, with JUnit (and even PHPUnit) an XML log file is produced by
>> the unit tests. There are a few xsl and xslt stylesheets that can
>
> Search the archive for 'test unit xml' and you'll find several  
> solutions.
>
> J.
>