From: ara.t.howard@... Date: 2006-05-16T23:47:15+09:00 Subject: Re: Forcing some code to run at the end of tests On Tue, 16 May 2006, Sy Ali wrote: > On 5/16/06, Vidar Larsen wrote: > >> It looks like the ordering is important. If you do: >> >> require 'test/unit' >> BEGIN{ puts '======== BEGIN ========' } >> END{ puts '======== END ========' } >> >> class ATest < Test::Unit::TestCase >> def test_a() assert true end >> end >> >> then the result will be: >> >> ======== BEGIN ======== >> ======== END ======== >> Loaded suite a >> Started >> . >> Finished in 0.001859 seconds. >> >> 1 tests, 1 assertions, 0 failures, 0 errors > > Yes, this is exactly what I was doing. Curious. it's because test/unit registers it's own blocks too. -a -- be kind whenever possible... it is always possible. - h.h. the 14th dali lama