aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/test/test_case_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Properly deprecate #pending from AS::TestCaseCarlos Antonio da Silva2012-11-181-0/+6
| | | | Check https://github.com/rails/rails/pull/4575#issuecomment-5765575.
* Make the tests pass with minitest 4.2Rafael Mendonça França2012-11-051-0/+3
|
* Exceptions like Interrupt should not be rescued.James Mead2012-05-281-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 nilAaron Patterson2012-01-061-0/+8
|
* No need to check if MiniTest::Assertions is definedRafael Mendonça França2012-01-061-32/+30
|
* fixing test case test on 1.9.3devAaron Patterson2011-03-011-0/+4
|
* calling correct method on minitest for test name when teardown callback failsAaron Patterson2010-10-041-0/+19
|
* [#5406 state:resolved] calling the correct method on minitest to obtain the ↵Aaron Patterson2010-10-041-0/+38
test name