Preventing API drift with contract tests

In an older post on his blog Adam Wathan shared an interesting approach on how to prevent API drift between a test mock and an actual implementation.

One of the risks of writing your own test doubles is that the API of the double can fall out of sync with the API of the real implementation.
In this screencast I walk through an example that explains:
 — How interfaces can provide a false sense of security
 — Why tests make better contracts than interfaces
 — How to run multiple implementations against a shared set of contract tests
If you’ve ever had issues with API drift, try this approach and let me know how it works for you.