I agree with the above - there is a good reason for us to test that we only update once in the integration test (as it is a user requirement, and behaviour that is worth testing against a real system), but using an rspec matcher to test this is inserting rspec into our code path, which is *bad* in an integration test.

I'll make sure that there is a unit test for this behaviour, and have a ponder as to how we can test there has been one one update non-intrusively.