Benjamin Fleischer 17d560eae4 Account for different handling of symbol keys in Rails 4.0 ... Comparing as a JSON string vs. as the Hash that is convert to JSON works around the different Hash representations. This likely has to do with the introduction of config.action_dispatch.perform_deep_munge in Rails 4.1 See Rails issue 13420 1) Failure: ActiveModel::Serializer::Adapter::Json::HasManyTestTest#test_has_many_with_no_serializer [active_model_serializers/test/adapter/json/has_many_test.rb:36]: --- expected +++ actual @@ -1 +1 @@ -{:id=>42, :tags=>[{"attributes"=>{"id"=>1, "name"=>"#hash_tag"}}]} +{:id=>42, :tags=>[{"attributes"=>{:id=>1, :name=>"#hash_tag"}}]} 2) Failure: ActiveModel::Serializer::AssociationsTest#test_has_many_with_no_serializer [active_model_serializers/test/serializers/associations_test.rb:74]: --- expected +++ actual @@ -1 +1 @@ -[{"attributes"=>{"name"=>"#hashtagged"}}] +[{"attributes"=>{:name=>"#hashtagged"}}]		2015-06-26 02:16:35 -03:00
..
json	Account for different handling of symbol keys in Rails 4.0	2015-06-26 02:16:35 -03:00
json_api	updating tests to work with new virtual_value implementation	2015-06-26 02:16:35 -03:00
fragment_cache_test.rb	removing unnecessary root parameter on fragment cache	2015-06-13 15:48:33 -03:00
json_test.rb	updating tests to match new adapters structure	2015-06-15 13:39:36 -03:00
null_test.rb	Remove 'Adapter' suffix from adapters since they are in Adapter:: namespace	2014-08-29 11:40:56 +04:00