Skip to content

Fix bug when Rails.application is defined but is nil. See #881 #6429

merged 1 commit into from May 21, 2012

3 participants


Got hit by this bug today. Credits should go to Josep M. Bach, see #881.

Ruby on Rails member

I remember having this issue while working on rails-api with @spastorino, the solution iirc was to actually define an application (ie inherit from Rails::Application somewhere in our test_helper).

@marcandre do you have a small example that shows the issue? I don't remember exactly how it happened at that time. Thanks!

Ruby on Rails member

it will probably happen in any gem that defines a railtie and uses integration testing.


It's possible I wasn't doing the right thing, but I needed an ActiveRecord based model in one test, so I created one ( ) and that had impact on another test ( ) because now the TestCase could not be instantiated anymore.

Maybe there is something else that could be fixed, but I feel the patch should be accepted. It's very possible that defining an application works, but it shoudn't be mandatory if it can be avoided.

Ruby on Rails member

Agreed, I just wanted to remember what was the use case, thanks for clarifying, I think mine at that time was a bit different, but I've got the same error. Anyway, the patch looks fine, thank you.

@carlosantoniodasilva carlosantoniodasilva merged commit c5fc159 into rails:master May 21, 2012
@derekcroft derekcroft pushed a commit to coupa/delocalize that referenced this pull request Nov 26, 2014
@clemens clemens Don't run tests in Rails 3.0/3.1 at the moment
Reason: rails/rails#6429 seems to not have been backported for 3.0/3.1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.