From: Matthias Lampert <ml@...>
Date: 2001-11-29T22:19:08+09:00
Subject: [ruby-talk:26889] Re: Small RubyUnit extension

Hi, Dave!

Also las ich bei Dave Thomas [mailto:Dave@PragmaticProgrammer.com]
> 
> [...]
>
> Another good approach, except... When I did the same for RubyUnit, and
> then decided to change the way I invoked the tests, I had to edit 50
> files. Using this newer approach there'd have been no change.

All right.  I simply didn't think of the possibilities of 
BEGIN{...} and END{...} when I made life a little easier for me; 
on the other hand I haven't had much need for being dynamic 
here so far.  Thanks to refactoring my classes keep clearly arranged 
most of the time (one file, one class, one chief), and in case 
I need some special treatment I put it right where it belongs.

The longer I do Ruby, however, I get more and more accustomed to 
automate writing scripts themselves and optimize for performance
later.

> > The existing RubyUnit distribution provides a very nice interface
> > for that (.../rubyunit-0.3.9.03a/sample/testall.rb).
> 
> That does something slightly different, running tests from multiple
> test files.

I forgot to mention the ubiquitous footer in the single test 
files there. This is the other skeleton I use. Sorry.

Regards,

--

Matthias.