From: Nathaniel Talbott <nathaniel@...>
Date: 2002-03-20T08:20:29+09:00
Subject: RE: Rubicon -> Test::Unit

Bil Kleb [mailto:W.L.Kleb@LaRC.NASA.Gov] wrote:

> Are there plans a foot for Rubicon to use Test::Unit?

Dave and I have discussed it... I think it will happen eventually, but
no definite plans have been made yet.


> I ask because we currently use Rubicon's BulkTestRunner
> to summarize our RubyUnit test results via

So you're looking for support for the BulkTestRunner capability under
native Test::Unit? If it's generally useful, perhaps it ought to move
out of Rubicon and in to the testing framework itself. I haven't looked
at the code, but I don't imagine it would be that hard.

Just so I can figure out what functionality ought to move and where it
ought to go, what are the features you find useful in the BulkTestRunner
over the Console::TestRunner?

<snip>

> Note: each TestSuite still has to use the old-syle RubyUnit
> format, otherwise all the tests are executed twice, e.g.,

What do you mean by RubyUnit format? The __FILE__ == $0 thing? Or
something else?


Nathaniel

<:((><
+ - -
| RoleModel Software, Inc.
| EQUIP VI