Rails validation error - NameError: TestCase :: SUPPORTS_INFO_SIGNAL

Question

In my Rails application, I upgraded Ruby from 1.9.3 to 2.1.0 . Now, when I restart my tests, I get an error message:

 NameError: uninitialized constant MiniTest::Unit::TestCase::SUPPORTS_INFO_SIGNAL 

Here are the gems in the Gemfile :

 gem 'rails' gem 'mysql2' gem 'json' gem 'jquery-rails' gem 'kaminari' gem 'therubyracer' gem 'devise' gem 'rak' gem 'rails-translate-routes' gem 'routes' group :assets do gem 'sass-rails', " ~> 3.2.3" gem 'uglifier', ' >= 1.0.3' end group :development, :test do gem 'factory_girl_rails' end group :test do gem 'shoulda' gem 'database_cleaner' gem 'capybara' end 

Here's the stack trace:

 `NameError: uninitialized constant MiniTest::Unit::TestCase::SUPPORTS_INFO_SIGNAL ~/.rvm/gems/ ruby-2.1.0@kalender /gems/mocha-0.10.5/lib/mocha/integration/mini_test/version_230_to_262.rb:19:in `run'` ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/testing/setup_and_teardown.rb:36:in `block in run' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/callbacks.rb:425:in `_run__4401979439353622961__setup__4295356768171603498__callbacks' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/callbacks.rb:405:in `__run_callback' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/callbacks.rb:385:in `_run_setup_callbacks' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/callbacks.rb:81:in `run_callbacks' ~/.rvm/gems/ ruby-2.1.0@kalender /gems/activesupport-3.2.12/lib/active_support/testing/setup_and_teardown.rb:35:in `run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:933:in `map' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:661:in `each' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:27:in `run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:780:in `run' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:33:in `run_once' ~/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun' 

Answer 1

I just stumbled upon an error that is similar or identical to this, and was able to solve it locally. For me, I had a trail that starts with:

 /home/youruser/.rvm/gems/ruby-2.1.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test/version_230_to_262.rb:19:in `run': uninitialized constant MiniTest::Unit::TestCase::SUPPORTS_INFO_SIGNAL (NameError) 

This shows that the error actually occurs in mocha when it tries to refer to a constant that was removed from the minitest version, which probably came along with your Ruby update.

For me, doing bundle update mocha fixes the problem.

Carrying out a little markup of the code to find out exactly where the problem was fixed, I used "git pickaxe" ( git log -SSUPPORTS_INFO_SIGNAL ) on the cloned copy of the mocha repository, and this looks like this commit removed the link to SUPPORTS_INFO_SIGNAL , so using anything after that fixation in mocha should be in order.

If updating your version of mocha doesn’t solve the problem, look carefully at the stack trace and you should see which of the libraries, which depends on MINITEST, with SUPPORTS_INFO_SIGNAL set, is causing an error. Then look upstream in this dependency to make sure this problem is fixed. If not, the plug of the dependency you are using displays this behavior and pushes your own patch upstream.