From 6158355f2eb51f6768c60077a177af370e95a14b Mon Sep 17 00:00:00 2001 From: Kasper Timm Hansen Date: Sat, 7 Nov 2015 11:35:01 +0100 Subject: [PATCH] Fix wrong `assert_equal` argument order. It goes expected, then actual. Only changed this because the file was just touched (please don't submit pull requests :)). --- activerecord/test/cases/connection_management_test.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/activerecord/test/cases/connection_management_test.rb b/activerecord/test/cases/connection_management_test.rb index 6f9ffed0f5..d43668e57c 100644 --- a/activerecord/test/cases/connection_management_test.rb +++ b/activerecord/test/cases/connection_management_test.rb @@ -92,14 +92,14 @@ module ActiveRecord app = lambda { |_| [200, {}, body] } response_body = ConnectionManagement.new(app).call(@env)[2] assert response_body.respond_to?(:to_path) - assert_equal response_body.to_path, "/path" + assert_equal "/path", response_body.to_path end test "doesn't mutate the original response" do original_response = [200, {}, 'hi'] app = lambda { |_| original_response } ConnectionManagement.new(app).call(@env)[2] - assert_equal original_response.last, 'hi' + assert_equal 'hi', original_response.last end end end