Removes hard-coded 'ENV['RAILS_ENV']=='test' check from railtie.rb

[Qqwy]

The hard-coded check in https://github.com/metaskills/minitest-spec-rails/blob/master/lib/minitest-spec-rails/railtie.rb#L6 made it impossible to use specs in custom testing environments.

Instead of hard-coding this, it makes more sense to include the code whenever the gem is loaded. (i.e. using the groups in the Gemfile).

[metaskills]

Hmmm... I'm sure this was here for some reason. Wont removing it mean that we would load a bunch of test code in other envs like prod? Maybe it is doing that anyway?

[Qqwy]

Wont removing it mean that we would load a bunch of test code in other envs like prod? Maybe it is doing that anyway?

According to the readme, the recommended way to use minitest-spec-rails is

group :test do
  gem 'minitest-spec-rails'
end

which would result in the gem only being loaded in the test environment.

If you want to use it in another environment, such as in e.g. a specialized benchmarking environment, you can change it to

group :test, :benchmarking do
  gem 'minitest-spec-rails'
end

As far as I understand how Bundle and Rails work, this should be enough to ensure that the code is included only when the app runs in this particular environment.

[metaskills]

Oh yea, good point. I'll merge this in and cut a new version.

[metaskills]

Now live on Rubygems v6.2.0. Thanks so much for taking the time to make a pull request. Cheers!

[Qqwy]

Thank you very much! Cheers! 💚