Well, I'm saying that we should be testing the default case, which is to query with the primary key. Testing the scope keys should be done only in the scope keys model spec. Any class configuration done for that spec shouldn't affect other specs.

As far as testing implementation vs. behavior, there are always trade-offs to be made. In this case, our library is supposed to grab the scope keys and so if we use the current configured scope keys in our spec (instead of manually listing the attributes we expect to see), we should cover both case.