title: Rails minitest returning "NoMethodError: undefined method `make_response!'"
body: <p>I have a couple tests that run fine independently</p>
  
  <pre><code>rails t test/controllers/briefs_controller_test.rb
  Running via Spring preloader in process 24174
  Run options: --seed 46330
  
  # Running:
  
  .................................
  
  Finished in 9.219203s, 3.5795 runs/s, 3.9049 assertions/s.
  33 runs, 36 assertions, 0 failures, 0 errors, 0 skips
  </code></pre>
  
  <p>But all together they produce </p>
  
  <pre><code>Running via Spring preloader in process 24023
  Run options: --seed 35139
  
  # Running:
  
  ..............................................................................................E
  
  Error:
  BriefsControllerTest#test_should_get_project_brief_by_admin:
  NoMethodError: undefined method `make_response!' for ProjectsController:Class
      test/controllers/briefs_controller_test.rb:9:in `block in &lt;class:BriefsControllerTest&gt;'
  
  
  bin/rails test test/controllers/briefs_controller_test.rb:7
  
  .....E
  
  Error:
  BriefsControllerTest#test_should_get_project_brief_by_brand:
  NoMethodError: undefined method `make_response!' for ProjectsController:Class
      test/controllers/briefs_controller_test.rb:15:in `block in &lt;class:BriefsControllerTest&gt;'
  </code></pre>
  
  <p>I was suspecting fixtures at first but only controllers test with <code>get</code> or <code>post</code> with <code>project</code> routes are crashing.</p>
  
  <pre><code>require 'test_helper'
  
  class BriefsControllerTest &lt; ActionDispatch::IntegrationTest
    include Devise::Test::IntegrationHelpers
    include I18n::Alchemy
  
    test "should get project brief by admin" do
      sign_in users(:admin)
      get project_brief_url(projects(:project_two).id)
      assert_response :success
    end
  
    test "should get project brief by brand" do
      sign_in users(:brand)
      get project_brief_url(projects(:project_one).id)
      assert_response :success
    end
  
  [end of test file removed for clarity ]
  </code></pre>
  
  <p>Any ideas ?</p>
  
  <p>This only happens on routes based on <code>projects</code> calls on other routes are fine.</p>