From: Chris Kottom <chris@...>
Date: 2011-07-28T18:29:09+09:00
Subject: Re: Test Unit setup teardown problem

--20cf30563961f9250604a91dcba0
Content-Type: text/plain; charset=UTF-8

I'm not sure whether it's possible to do what you're suggesting.  It's open
source, so I'm sure that if you're properly motivated to do so you could
monkeypatch this into Test::Unit.  The point, though, is that you want to be
testing your objects' behavior against a known state, not just whatever
happens to be hanging around from any other tests you've already performed.
 If you're relying on the results or state set by one test in order to pass
another, I'd call that a code smell, and I'd start looking for ways to
rethink or refactor.

On Thu, Jul 28, 2011 at 10:39 AM, Gaurang Shah <shahgomji@gmail.com> wrote:

> Hi All,
>
> I am using Test::Unit framework for website testing. It has setup and
> teardown methods. The thing is it is called before and after each and
> every test methods.
>
> is there any way we can call setup method before first test gets execute
> and teardown method after last test executes rather than before and
> after each and every test???
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--20cf30563961f9250604a91dcba0--