Why does running a Test::unit test in irb work so weirdly?

[Peter Recore]

Why can't I run a Test::Unit::TestCase from IRB and have it run before I
quit?
I have found this problem mentioned by others. For an example, see this
tutorial about testing:

http://www.nullislove.com/2007/11/14/testing-in-rails-part-1-unit-testing-in-ruby/

irb --simple-prompt

Loaded suite irb
Started
F
Finished in 0.00119 seconds.

The author mentions that a quirk of irb makes this happen but doesn't
say what the quirk is:

"When we finished the definition, nothing happened. When we exited IRB,
then our tests ran. That’s a characteristic of using IRB for our tests
and won’t be significant as we move on."

Thanks for any insight you have.

 

[Christopher Dicely]

Why can't I run a Test::Unit::TestCase from IRB and have it run before I
quit?

You can, you just have to explicitly tell it to run. Normally, you
don't explicitly run Test::Unit tests, you simply define them and then
they run automagically when ruby exits, because the Test::Unit
library, when it is loaded, loads an at_exit routine that will (unless
something has told it not too) run the tests that have been defined.
Its not really an IRB quirk that stops them from running until you
exit, its just that when you run a script with unit tests
"standalone", you don't realize that the tests are run when it is
exiting. With IRB, you just notice what is going on regularly when you
use Test::Unit.

The RDoc for Test::Unit gives this example of how to explicitly run a test case:

require 'test/unit/ui/console/testrunner'
Test::Unit::UI::Console::TestRunner.run(TC_MyTest)