1. Introduction to Unit Testing and Mocking Joe Wilson, President Volare Systems, Inc. Email: joe@volaresystems.com Office: 303-532-5838, ext 101 Web: http://VolareSystems.com Blog: http://VolareSystems.com/Blog Twitter: joe_in_denver

2. Quick Audience Poll Who has done unit testing? Who has tried and given up?

3. Agenda What is unit testing? Step-by-step What is mocking? Dos and Don’ts

5. Not touching anything external (DB, file, etc.)

6. The developer’s job

8. Smaller, tighter, decoupled code

9. Documentation of requirements

10. Continuous integration

13. Still need integration testing

14. Still need user-acceptance testing

15. May want UI testing

17. Thinking about how code will be consumed

18. Stop coding when reqs met

19. Harder initially

20. Focus on code

21. Thinking about algorithm

22. More refactoring

24. Recipe– Unit Test Project Create unit test project Add references Create project folders

25. Recipe – Unit Test Class One unit test class per class under test Name it for your class under test, like *Tests Add using for testing framework Add [TestFixture] attribute

26. Recipe – Unit Test Class Using Test class per class Name *Tests [TestFixture] attribute

28. <MethodUnderTest>_<condition>_<outcome>()

30. Recipe – Unit Test Method (BDD Style) Context Because Observation

32. Setup code, prerequisites, etc.

33. Act

34. One line

35. Exercise method under test

36. Assert

38. Code!

39. Recipe – Pull Out a Dependency Wrap dependency with an interface Create a private field of interface type Add interface as an argument in the constructor Assign private field to argument in constructor Use the new private field in code

40. Code!

42. Nothing you can’t do manually

43. Set and inspect values on a fake object

46. Set method return values

47. Test state

48. Check method calls

49. Check arguments used

51. Code!

53. One logical assert

54. Code to abstractions, wrap difficult code

55. Prefer state testing over interaction

56. AAA syntax to keep organized

58. Test code you didn’t write (BCL, 3rd party)

59. Order tests (integration test)

60. Overuse Setup or Teardown (integration test)