rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Properly deprecate #pending from AS::TestCase	Carlos Antonio da Silva	2012-11-18	1	-0/+6
\| \| \| \|	Check https://github.com/rails/rails/pull/4575#issuecomment-5765575.
*	Make the tests pass with minitest 4.2	Rafael Mendonça França	2012-11-05	1	-0/+3
\|
*	Exceptions like Interrupt should not be rescued.	James Mead	2012-05-28	1	-8/+50
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	make sure the test case name is nil	Aaron Patterson	2012-01-06	1	-0/+8
\|
*	No need to check if MiniTest::Assertions is defined	Rafael Mendonça França	2012-01-06	1	-32/+30
\|
*	fixing test case test on 1.9.3dev	Aaron Patterson	2011-03-01	1	-0/+4
\|
*	calling correct method on minitest for test name when teardown callback fails	Aaron Patterson	2010-10-04	1	-0/+19
\|
*	[#5406 state:resolved] calling the correct method on minitest to obtain the ↵	Aaron Patterson	2010-10-04	1	-0/+38
	test name