OK, I see now. So please bear with me...I'm new to both rspec and ruby. Sometimes it takes me a second to see what's actually happening.

Normally I'd think the ordering of tests is (should be) irrelevant, since each one should be run with a fresh instance and be deterministic, not relying on anything that's happened in other tests, or the time of day, or any other state besides what was set up in the test fixture.

But, that's not the case here. Not really because of anything about the test, but because of `@@crmready`. I'd argue that this is a bad smell in itself: the smell of mutable global state. If it was surprising in this test, it will be surprising in real usage also. Since it's not clear to me what problem `ready?` was solving in the first place, and this PR doesn't make it any more clear, while adding this new smell, :-1: