Hi Jano
>
> I have looked at the code,

Thanks I feel isolated working on this code on my own. Your effort is
greatly appreciated.


> I wonder why do you use Test::Unit, when you barely use its features
> (by that I mean especially no asserts in the code). If it is indeed
> the case (no hidden asserts somewhere in the unpublished code), it
> might be easier to run your cases by your code.

I just wanted to use the setup and teardown methods but maybe I am
forcing a solution that doesn't fit my problem.

>
> Another way how to solve it would be to create custom TestSuite, that
> would set the data and call the test case.
>
> class RepeatingTestSuite < Test::Unit::TestSuite
>         def initialize(count=1, name="Unnamed TestSuite")
>                 super(name)
>                 @count = count
>         end
>
>         def run(result, &progress_block)
>                 # set your data here
>                 @count.times do
>                         super
>                 end
>         end
>
>         def size
>                 return @count * super
>         end
> end
>
> class TS_MyTests
>         def self.suite
>                 suite = RepeatingTestSuite.new(2)
>                 suite << Test_Suite_1.suite
>                 return suite
>         end
> end

I will try
>
> BTW. using a lot of @@ class variables is a mark of a bad design
> IMHOI... not always, but usually. Maybe splitting into more classes
> will help.

Good point. I will refactor
>
> And have a look at test/unit sources if you haven't done
> already...there's much more info that in the docs. Most of the code is
> easy, except that throw/catch part in the TestCase ;-)
>
Thanks

Aidy