Sometimes there’s a path in a service or application that you want to test where all it does is log something and return. You could check other things, but sometimes it is hard to check to see if something didn’t happen… and it would be a lot easier to know if something did happen, like … [Read more…]
Unit testing can be annoying. Sometimes it feels like setting up a delicate house of cards in just the right way and hoping that nobody opens a window to let a breeze knock the whole thing over. If you’re using inversion of control (and you should be), its a little easier because you can use … [Read more…]
In the last blog post I talked about how to use Moq’s built in SetupSequence to create a “chain” of actions to execute for subsequent calls of the same mocked method. This works great for the simple case, but falls down when you have to do something a little more complicated like, say, issue a … [Read more…]
Say that you’re unit testing and you want a mocked interface to behave differently for different calls to the same method. I was trying to test a TCP listener loop – a TcpListener waits for an incoming connection, does something with it, and then goes back to listening. In essence, the loop will last until … [Read more…]