tests would fail when run in a certain order because the way Slanger::Redis was set up to listen for messages. if the file was first loaded when EM::Hiredis.connect was stubbed the object would not receive messages for the rest of the test suite causing the integration tests to hang forever. the opposite case was that EM::Hiredis.connext was never mocked if the tests were green in particular order. fixed by explicitly deleting connections from Slanger::Redis before and after they are mocked and making pubsub subscription lazy instead of eager.