6 Commits

Author	SHA1	Message	Date
James Mead	b057fab638	Exceptions like Interrupt should not be rescued. ... Neither Test::Unit nor MiniTest rescue exceptions like Interrupt or NoMemoryError, but ActiveSupport::Testing::SetupAndTeardown#run which overrides MiniTest::Unit::TestCase#run rescues them. Rescuing an Interrupt exception is annoying, because it means when you are running a lot of tests e.g. when running one of the rake test tasks, you cannot break out using ctrl-C. Rescuing exceptions like NoMemoryError is foolish, because the most sensible thing to happen is for the process to terminate as soon as possible. This solution probably needs some finessing e.g. I'm not clear whether the assumption is that only MiniTest is supported. Also early versions of MiniTest did not have this behaviour. However, hopefully it's a start. Integrating with Test::Unit & MiniTest has always been a pain. It would be great if both of them provided sensible extension points for the kind of things that both Rails and Mocha want to do.	2012-05-28 22:44:28 +01:00
Aaron Patterson	f65559fcc2	make sure the test case name is nil	2012-01-06 15:17:08 -08:00
Rafael Mendonça França	b2fca9533e	No need to check if MiniTest::Assertions is defined	2012-01-06 13:31:39 -03:00
Aaron Patterson	e477fc1147	fixing test case test on 1.9.3dev	2011-03-01 10:14:09 -08:00
Aaron Patterson	b7c49cedba	calling correct method on minitest for test name when teardown callback fails	2010-10-04 09:34:34 -07:00
Aaron Patterson	ccf228b027	[#5406 state:resolved] calling the correct method on minitest to obtain the test name	2010-10-04 09:33:35 -07:00