Minitest references Rails in non-Rails code

[soulcutter]

Given a file "minitest.rb" that requires minitest/autorun
And minitest 5.22.3 is being used
When I run ruby -Ilib:test ./minitest.rb

I get the output on a failing test:

bin/rails test ./minitest.rb:5

This file does not require any rails, there is no Gemfile, AFAIK nothing that might load any rails thing. bin/rails does not exist at this location. I would expect there be no reference to Rails.

Here's minitest.rb

require 'minitest/autorun'

class MyTestThatProducesADiff < Minitest::Test

  def test_diff
    assert_equal "Mayonnaise is delicious", "Mayonnaise is delicioous"
  end
end

Output

$ ruby -Ilib:test ./minitest.rb
Run options: --seed 43692

# Running:

F

Failure:
MyTestThatProducesADiff#test_diff [./minitest.rb:6]:
Expected: "Mayonnaise is delicious"
  Actual: "Mayonnaise is delicioous"


bin/rails test ./minitest.rb:5



Finished in 0.000435s, 2298.8505 runs/s, 2298.8505 assertions/s.
1 runs, 1 assertions, 1 failures, 0 errors, 0 skips

In case it might be getting polluted from something automatically trying to require rails, here's a filtered list of what gems are present (but not required in my code):

$ gem list | grep rails
autoprefixer-rails (10.4.16.0)
dotenv-rails (3.1.0)
factory_bot_rails (6.4.3)
pry-rails (0.3.9)
rails (7.1.3.2)
rails-dom-testing (2.2.0)
rails-html-sanitizer (1.6.0)
rspec-rails (6.1.2)
ruby-lsp-rails (0.3.5, 0.3.3)
sass-rails (6.0.0)
sassc-rails (2.1.2)
sprockets-rails (3.4.2)

[blowmage]

Minitest plugin system looks at all installed gems, so its possible you have a plugin installed that is altering the behavior.

Here is what your test looks like in a clean gemset on my system:

 >> chruby 3.3.1

 >> ruby -v
ruby 3.3.1 (2024-04-23 revision c56cd86388) [arm64-darwin23]

 >> omg clean
Switching gemset to clean

 >> gem install minitest
Fetching minitest-5.22.3.gem
Successfully installed minitest-5.22.3
1 gem installed

 >> echo 'require "minitest/autorun"\n\nclass MyTestThatProducesADiff < Minitest::Test\n\n  def test_diff\n    assert_equal "Mayonnaise is delicious", "Mayonnaise is delicioous"\n  end\nend' > clean_test.rb
 
 >> cat clean_test.rb
require "minitest/autorun"

class MyTestThatProducesADiff < Minitest::Test

  def test_diff
    assert_equal "Mayonnaise is delicious", "Mayonnaise is delicioous"
  end
end

 >> ruby ./clean_test.rb
Run options: --seed 59813

# Running:

F

Finished in 0.000258s, 3875.9690 runs/s, 3875.9690 assertions/s.

  1) Failure:
MyTestThatProducesADiff#test_diff [./clean_test.rb:6]:
Expected: "Mayonnaise is delicious"
  Actual: "Mayonnaise is delicioous"

1 runs, 1 assertions, 1 failures, 0 errors, 0 skips

[soulcutter]

https://github.com/minitest/minitest?tab=readme-ov-file#writing-extensions-

➜  temp irb             
>> Gem.find_files("minitest/*_plugin.rb")
=> 
["/Users/bradleyschaefer/.asdf/installs/ruby/3.3.0/lib/ruby/gems/3.3.0/gems/minitest-5.22.3/lib/minitest/pride_plugin.rb",
 "/Users/bradleyschaefer/.asdf/installs/ruby/3.3.0/lib/ruby/gems/3.3.0/gems/minitest-5.20.0/lib/minitest/pride_plugin.rb",
 "/Users/bradleyschaefer/.asdf/installs/ruby/3.3.0/lib/ruby/gems/3.3.0/gems/railties-7.1.3.2/lib/minitest/rails_plugin.rb",
 "/Users/bradleyschaefer/.asdf/installs/ruby/3.3.0/lib/ruby/gems/3.3.0/gems/simplecov-0.22.0/lib/minitest/simplecov_plugin.rb"]

I don't suppose that behavior is up for re-examination. I will register my personal comment that the result of this design is behavior that I would not expect. Thanks.