…ation such as --seed.
…ub.com/randycoulman/minitest-reporters into develop
minitest-4.1.0 and earlier send record from _run_suite, which is after all of the test lifecycle callbacks have happened. To deal with this, record now sends after_test on older versions of minitest, and after_test checks for nil runners and returns early in that case.
This reverts commit 865b608. That commit doesn't fix the problem with mintest-3.5.0.
When there is a failure or exception in a :teardown, ProgressReporter was counting the test twice, resulting in a > 100% completion percentage. RubyMineReporter was counting the additional failure or error as a separate test and logging a warning to the console. * Add an :after_test callback to the reporters. * Rename DefaultReporter's now-conflicting :after_test to :test_result. * Both reporters report test completion status in after_test instead of in the various pass/fail/etc. methods.