It can happen sometimes that the test setup is incorrect and the code under test is similarly bad, resulting in both values for a key being nil. As the library is currently written, this will pass. It should stay the default behavior, I think, but we should look at adding an option that will raise if both values for a key are nil.
It can happen sometimes that the test setup is incorrect and the code under test is similarly bad, resulting in both values for a key being nil. As the library is currently written, this will pass. It should stay the default behavior, I think, but we should look at adding an option that will raise if both values for a key are nil.