Does an RSpec2 matcher for matching Hashes exist?

Question

Note to future readers: think RSpec does not consider your Hashes equal? One might be an OrderedHash, but from the regular RSpec output you can't tell. This was the problem that prompted this post.

Original question:

Suppose I have a spec where I want to test that a method generates the appropriate Hash.

it 'should generate the Hash correctly' do
  expected = {:foo => 1, 'baz' => 2}
  subject.some_method_that_should_generate_the_hash.should == expected
end

This often fails, because different Hashes with the same key-value pairs may return their pairs in a different ordered. Results look like:

Failure/Error: subject.some_method_that_should_generate_the_hash.should == expected
expected: {:foo => 1, 'baz' => 2},
     got: {'baz' => 2, :foo => 1}

For arrays, this is solved using the =~ operator. However, that does not work for Hashes. For now, I've resorted to

it 'should generate the Hash correctly' do
  expected = {:foo => 1, 'baz' => 2}
  subject.some_method_that_should_generate_the_hash.each {|k,v|
    v.should == expected[k]
  }
end

but that seems unnecessarily verbose. I expect there to be an obvious solution for this. Am I overlooking something in the docs or doesn't RSpec have a proper Matcher for orderless Hash equality?

score 19 · Accepted Answer · answered Jan 18 '11 at 23:19

19

describe 'Hash' do
  let(:x) { { :a => 1, :b => 2 } }
  let(:y) { { :b => 2, :a => 1 } }

  it "should be equal with ==" do
    x.should == y
  end
end

Passes. I'm not sure what's going on in your specific case. Do you have some failing examples you can share?

Programming Ruby has this to say:

Equality — Two hashes are equal if they have the same default value, they contain the same number of keys, and the value corresponding to each key in the ﬁrst hash is equal (using ==) to the value for the same key in the second.

answered Jan 18 '11 at 23:19

zetetic

47,184
10
111
119

Yesterday late I found the problem: I was not actually comparing two Hashes: one had turned into an OrderedHash somewhere along the way. You can't glance that from the RSpec output and I'm a bit embarrassed to say this wasn't the first time I fell into this trap either :/ – Confusion Jan 19 '11 at 06:08
3

Interesting. So an OrderedHash and a Hash with the same key/value pairs are not considered equal -- that's good to know. – zetetic Jan 19 '11 at 07:33

score 7 · Answer 2 · answered Jul 07 '12 at 18:30

7

Since 8 months the gem rspec-matchers has support for matching hashes:

expected.should be_hash_matching(subhash_or_equal)

see here for more details: https://github.com/rspec/rspec-expectations/pull/79

answered Jul 07 '12 at 18:30

Niklas Hofer

112
1
3

this seems to have been removed in rspec 3, but `.to eql(x)` works – nruth Apr 27 '16 at 16:18

score 5 · Answer 3 · answered Jan 18 '11 at 22:51

5

I believe the eql? method checks only that the two hashes have the same content So IIRC in Rspec2 you can do:

    expected = {:foo => 1, 'baz' => 2}
    expected.should be_eql({'baz' => 2, :foo => 1})

And the test should pass

answered Jan 18 '11 at 22:51

Kyle d'Oliveira

6,382
1
27
33

or in rspec 3, `expect(x).to eql(y)` – nruth Apr 27 '16 at 16:18

Does an RSpec2 matcher for matching Hashes exist?

3 Answers3

Linked