It’s really important to break through the record/replay concept, even though that’s how it’s expressed in Rhino. It puts too much emphasis on shadowing the implementation of the object under test, rather than describing its relationship with its neighbours, and the result is usually brittle.

I try to think of interaction tests as saying: I have this object, to perform this action it will need the following services from its neighbours, now let’s see what happens.