This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Use setup & teardown!
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
In the process of tinkering with devel/logger, I'm pretty much rewriting the entire test suite. One of the things I see the author doing is setup and teardown within the tests themselves.
Don't do that. That's why you have the setup and teardown methods. Otherwise, you're wasting a lot of time and effort, and unnecessarily increasing the size of your test suite.
So, instead of this repeated ad nauseum:
def test_foo
fh = File.open("test","w+")
assert(some stuff with fh)
fh.close
File.unlink("test") if File.exists?("test")
end
def test_bar
fh = File.open("test","w+")
assert(some stuff with fh)
fh.close
File.unlink("test") if File.exists?("test")
end
Just do something like this:
def setup
@fh = File.open("test", "w+")
end
def test_foo
assert(some stuff with @fh)
end
def test_bar
assert(some stuff with @fh)
end
def teardown
@fh.close rescue nil
File.unlink("test") if File.exists?("test")
end
Previous Topic
