On Wed, 10 Jan 2001, Dave Thomas wrote:

> You also use setup methods to do things like tidy up external
> resources (databases, files and the like).
> 
I think I read somewhere that there is a good reason why a unit testing
framework shouldn't have setup_once and teardown_once for tidying up
external resources but I fail to remember the reason. Anyone knows the
reason? If not why dont we add setup_once to RubyUnit?

I often feel the need for such a thing (of course easily implemented with 
something a la!?):

class MyTestCase < RUNIT::TestCase
  @@setupped_once = nil
  def setup_once
    if !@@setupped_once
      @@setupped_once = true
      # Code goes here...
    end
  end

  def setup
    setup_once
    # Ordinary setup goes here...
  end
end

etc...

Regards,

Robert