Daniel Berger wrote:

> Hm, something's goofy. I just noticed that instance variables aren't 
> surviving more than one test. Using the applied patches, I tried this:

> TEARDOWN: '1'
> .SETUP: '' <- Hey, what happened?

That behavior is by design. The "test isolation" ideal implies you shouldn't 
need to work too hard to get a clean slate each time a test case starts. 
Otherwise a test could rely on a @value from the previous test, and could rely 
on it in a way you don't notice.

Of course any other persistent variable could ruin test isolation. We don't stop 
and restart Ruby between each test case. But at least when it happens the @ 
instance variables won't be to blame.

-- 
   Phlip