Five unit testing tips #4: Don't mock your way into accidental complexity