Thanks George.
I am following that advice also (already) so very good to get affirmation
of that.
However, I realize my question was not clear enough so continuing from your
answer, do you always verify behavior on mocked adaptors or are there
occasions where you don't? That is, you just mock them but don't verify.
I hope my question is clearer.
Eb
On Thu, Jul 11, 2013 at 4:16 PM, George Dinwiddie
<lists@...>wrote:
**
Eb,
On 7/11/13 2:28 PM, Eb wrote:
Hi everyone -
What criteria do you use to determine if a collaborator that is a
third-party should be mocked and the test should verify that the
collaborator was indeed called when it was supposed to be?
I wouldn't do that. I use adapters for third-party collaborators and
mock my adapters to verify behavior. I also write integration tests for
the adapter's interaction with the third-party.
Steve Freeman's advice is to never mock something you don't own. I've
only violated that advice when I needed to simulate error conditions
while testing my adapter.
- George
--
Want to speak at AgileDC October 8, 2013?
----------------------------------------------------------
* George Dinwiddie *
Software Development
Consultant and Coach
----------------------------------------------------------
--
blog:
twitter: @eikonne
