From: "bpettichord@..." <bpettichord@...>
Date: 2006-05-23T03:58:29+09:00
Subject: Re: Test::Unit Patch that allows test methods to be executed sequentially

Ryan sez:
> I do it all the time. The simple solution is to put a "test_dummy" in
> the superclass. Really not hard and a fair tradeoff to have the right
> code in the right place.

This has been suggested before to the Watir users. Many of them don't
like the fact that this results in an incorrect test case count.

>> I think the ideal solution would be to refactor the TestCase code
>> along
>> the lines of this patch, and thereby expose
>> TestCase.sorted_test_methods so that it could then be overlayed by
>> Modules.
>
> I disagree. As I said before, we need less code, not more. (I do
> wholly agree that test/unit needs refactoring, but to make it thinner
> not thicker)

My suggestion is only to add a new seam, but i guess that amounts to a
bit of code. But only a bit.

Another reason that i packaged the code as a mod to TestCase directly
is that it makes it easier for people with large test suites to plug it
in. So it is more convenient for Watir users than a subclass.

However, I'm not quite sure whether you are saying
a) i (ryan) would prefer to do it a different way
b) i don't want to see this change made to the core test/unit code in
ruby
c) it is a bad idea for anyone to use this mod

I understand (a). I can see your reasons for (b), and actually have
been eager for feedback on whether this might be a good idea or not.
(although i did get some positive noises offline from Nathaniel Talbott
-- the test/unit author). i can see no grounds for (c) -- if this is
your position, please elaborate.

Bret