rails--rails/railties/lib/rails/commands/test.rb

require "rails/test_unit/minitest_plugin"

if defined?(ENGINE_ROOT)
  $LOAD_PATH << File.expand_path("test", ENGINE_ROOT)
else
  $LOAD_PATH << File.expand_path("../../test", APP_PATH)
end

Minitest.run_via[:rails] = true

require "active_support/testing/autorun"
Improve test runner's Minitest integration. This also adds free mix and matching of directories, files and lines filters. Like so: bin/rails test models/post_test.rb test/integration models/person_test.rb:26 You can also mix in a traditional Minitest filter: bin/rails test test/integration -n /check_it_out/ 2015-03-21 08:15:56 -04:00			`require "rails/test_unit/minitest_plugin"`
spike of a `OptionParser` backed test runner. 2014-12-30 04:17:30 -05:00
make test runner work correctly inside engine 2015-07-12 04:51:35 -04:00			`if defined?(ENGINE_ROOT)`
improve test coverage 2016-09-16 12:26:10 -04:00			`$LOAD_PATH << File.expand_path("test", ENGINE_ROOT)`
make test runner work correctly inside engine 2015-07-12 04:51:35 -04:00			`else`
improve test coverage 2016-09-16 12:26:10 -04:00			`$LOAD_PATH << File.expand_path("../../test", APP_PATH)`
make test runner work correctly inside engine 2015-07-12 04:51:35 -04:00			`end`
Revise setting of run_with_rails_extension. The Rails test runner supports three ways to run tests: directly, via rake, or ruby. When Running with Ruby ala `ruby -Itest test/models/post_test.rb` our test file would be evaluated first, requiring `test_helper` and then `active_support/testing/autorun` that would then require the test file (which it hadn't been before) thus reevaluating it. This caused exceptions if using Active Support's declarative syntax. Fix this by shifting around when we set the how we're run to closer mimick the require order. If we're running with `bin/rails test` the test command file is run first and we then set `run_with_rails_extension`, later we hit `active_support/testing/autorun` and do nothing — because we've been run elsewhere. If we at this point haven't set `run_with_rails_extension` we've been running with `ruby` this whole time and thus we set that. We should always trigger `Minitest.autorun` as it doesn't hurt to call it twice. Consolidate the two methods into a single one that better brings out the intent of why they're there. 2016-09-25 14:21:30 -04:00
			`Minitest.run_via[:rails] = true`

			`require "active_support/testing/autorun"`