From: Suraj Kurapati Date: 2011-02-15T15:56:24+09:00 Subject: [ruby-core:35238] [Ruby 1.9-Bug#4400] nested at_exit hooks run in strange order Issue #4400 has been updated by Suraj Kurapati. By the way, this issue is not contrived. It prevents propagation of a proper exit status when using Test::Unit with Capybara (Selenium driver) where a unit test (run from Test::Unit's at_exit hook) loads the Capybara library which registers an at_exit hook of its own. As a result, Test::Unit always exits with 0 status, even if there were assertion failures, because Capybara's at_exit hook runs *after* Test::Unit's at_exit hook and overrides its exit status setting. See this bug report for full details: https://github.com/jnicklas/capybara/issues#issue/178/comment/658647 ---------------------------------------- http://redmine.ruby-lang.org/issues/show/4400 ---------------------------------------- http://redmine.ruby-lang.org