1. Interaction testing using mock objects 4

3. Understand mock objects

4. Mock vs Stub

5. Mock object best practices

7. action-driven testing

8. Watering system example

10. Verify object interact as expected

11. Decide whether the unit test has passed or failed

13. Assert is perform on mock LogError(string) Test LogAnalyzer MockWebService :IWebService Test

15. Save some state for later assertion and verification

16. Test spy (xUnit Test Pattern)

20. We’ll assert against mock that it was called correctly LogError(string) SendMail() Assert LogAnalyzer EmailService WebService Test

23. It is tedious to create manual mocks and stubs. How can we overcome that?

24. Could we use a Mock object as Stub?

26. No more than one mock

27. Stubs all other fake objects

28. If you need more mocks? in a test, you are testing more than one thing.

30. Chains of lie - “ phishing ” attack

31. Override virtual method

32. Create special wrapper classes to avoid chains

34. It's difficult to implement when interface have many properties, methods and events

35. A lot of boilerplate code to save data

36. Multiple assertions for method with more parameters

37. Hard to reuse for other tests

39. If you see “verify” and “stub” on the same variable in the same test, you most likely are over-specifying your test.

40. Just make sure your test remains readable .

41. Use mocking framework