From: Alexandru Popescu <the.mindstorm.mailinglist@...>
Date: 2006-07-01T10:00:34+09:00
Subject: Re: Forcing some code to run at the end of tests

Not sure I have correctly read this thread and not sure if this helps
(because it is something from JUnit which seems to have some common
ideas): in JUnit you can achieve this behavior by using a TestSetup.
It will allow you to run a method once before all your tests and
another method once after all your tests.

TestNG (http://testng.org), an alternative testing framework for Java
is defining more such places by allowing you to define methods to be
run @Before suite, test, group, class, methods and respectively
@After.

./alex
--
.w( the_mindstorm )p.
---
Co-founder TestNG

On 7/1/06, Patrick Spence <patrick@pkspence.com> wrote:
> Brian Cowdery wrote:
>
> <snip>
>
> > class ExampleTest < BetterTestCase #<< error here >>
> >
> >  def startup
> >     #do somthing once before any tests are run
> >  end
> >
> >  def close
> >     #do somthing after all tests are run
> >  end
> >
> >  def test_0010_somthing
> >     #test somthing...
> >  end
> >
> > end
>
> When I try to run this script, I'm getting a "uninitialized constant
> BetterTestCase (NameError)" error on line indicated above. Ideas anyone?
>
> --
> Posted via http://www.ruby-forum.com/.
>
>