From b9465e8755509cc79ad7492914a26c8ac3884de0 Mon Sep 17 00:00:00 2001 From: Kasper Timm Hansen Date: Tue, 22 Mar 2016 21:17:45 +0100 Subject: Set Rails as the first minitest initialized plugin. When calling `load_plugins` minitest would fill out its extensions, then we'd tackle ourselves on as the last plugin. Because minitest loads plugins in order we will ultimately have the last say on what reporters will be used. Invert that strategy by putting ourselves first and give other plugins plenty of leeway to override our default reporter setup. Fixes #24179. --- railties/lib/rails/test_unit/minitest_plugin.rb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'railties') diff --git a/railties/lib/rails/test_unit/minitest_plugin.rb b/railties/lib/rails/test_unit/minitest_plugin.rb index f22139490b..e1ba501a47 100644 --- a/railties/lib/rails/test_unit/minitest_plugin.rb +++ b/railties/lib/rails/test_unit/minitest_plugin.rb @@ -93,5 +93,7 @@ module Minitest mattr_accessor(:run_with_rails_extension) { false } end +# Let libraries override our reporter setup by loading other plugins then +# setting ourselves as the first plugin to be initialized. Minitest.load_plugins -Minitest.extensions << 'rails' +Minitest.extensions.unshift 'rails' -- cgit v1.2.3