It is often not helpful to write a unit test to simply ensures that method A is called, then method B, then method C (or whatever). That's just going to test that your implementation is your implementation, and it's likely to hinder rather than help the next developer who wants to refactor the code.