Downloaded 404 times
Uploaded byJoe Wilson
Unit Testing And Mocking
This document provides an introduction to unit testing and mocking. It discusses the benefits of unit testing such as safer refactoring and value that increases over time. It provides a recipe for setting up a unit test project with test classes and methods using AAA syntax. It also covers what mocking is and how to use mocking frameworks to create fake dependencies and check interactions. Resources for learning more about unit testing and related tools are provided.
More Related Content
Similar to Unit Testing And Mocking
Unit Testing And Mocking
- 1. Introduction to UnitTesting and MockingJoe Wilson, PresidentVolare Systems, Inc.Email: joe@volaresystems.comOffice: 303-532-5838, ext 101Web: http://VolareSystems.comBlog: http://VolareSystems.com/BlogTwitter: joe_in_denver
- 2. Quick Audience PollWhohas done unit testing?Who has tried and given up?
- 3. AgendaWhat is unittesting?Step-by-stepWhat is mocking?Dos and Don’ts
- 4. What is unittesting?Testing one thing at a time
- 5. Not touching anythingexternal (DB, file, etc.)
- 6.
- 7. Writing and refactoringcodeBenefits of unit testingSafer refactoring
- 8.
- 9.
- 10.
- 11. Value of testsincrease over timeBenefits of unit testingRev 1Rev 3Rev 2Benefit$CostTime – Life of System
- 12. Where does unittesting fit?Still need manual testing, hopefully less
- 13. Still need integrationtesting
- 14. Still need user-acceptancetesting
- 15. May want UItesting
- 16. May want performancetestingWhat do you need?Testing frameworkNUnit, MSTest, MbUnitTest runnerNUnit, MSTest, ReSharper, TDD.NETMocking frameworkRhino Mocks, Moq, TypeMockWhen do you write the test?Before coding (TDD, BDD)After/During codingFocus on requirements
- 17. Thinking about howcode will be consumed
- 18. Stop coding whenreqs met
- 19.
- 20.
- 21.
- 22.
- 23. Easier initiallyRecipe– UnitTest ProjectOne unit test projectName it after your solution, like *.UnitTestsUse Project Folders inside the project for namespacesSet testing framework and project references
- 24. Recipe– Unit TestProjectCreate unit test projectAdd referencesCreate project folders
- 25. Recipe – UnitTest ClassOne unit test class per class under testName it for your class under test, like *TestsAdd using for testing frameworkAdd [TestFixture] attribute
- 26. Recipe – UnitTest ClassUsingTest class per className *Tests[TestFixture] attribute
- 27. Recipe – UnitTest MethodOne unit test method per scenario Add [Test] attribute to a void methodPopular method naming patterns:Should_<outcome>_when_<condition>()
- 28.
- 29. BDD style –class and method names are specsRecipe – Unit Test Method[Test] attributeVoid methodTest method per scenario
- 30. Recipe – UnitTest Method (BDD Style)ContextBecauseObservation
- 31. Recipe – Arrange,Act, AssertArrange
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. One logical assertper testRecipe – Arrange, Act, AssertStart with Act to hit the methodMove onto Arrange to set conditionsEnd with Asserts
- 38.
- 39. Recipe – PullOut a DependencyWrap dependency with an interfaceCreate a private field of interface typeAdd interface as an argument in the constructorAssign private field to argument in constructorUse the new private field in code
- 40.
- 41. What is mocking?Creatingfake objects for you
- 42. Nothing you can’tdo manually
- 43. Set and inspectvalues on a fake object
- 44. Inspect method callsand args on a fake objectTwo kinds of unit testsBlack BoxWhite BoxStateInteraction
- 45. Stub vs. MockStubMockGet/Setproperties
- 46. Set method returnvalues
- 47.
- 48.
- 49.
- 50. Test interactionsRecipe –Mocking*Use the MockRepository.GenerateMock<T>() If you need a return value, use myMock.Stub().If the mock is a void, use the myMock.AssertWasCalled().* Paraphrased from Jimmy Bogard’s Los Techies blog
- 51.
- 52. Unit Testing DosOnetest per scenario
- 53.
- 54. Code to abstractions,wrap difficult code
- 55. Prefer state testingover interaction
- 56. AAA syntax tokeep organized
- 57. Use mocking toolfor dependenciesUnit Testing Don’tsIgnore failing tests (fix them immediately)
- 58. Test code youdidn’t write (BCL, 3rd party)
- 59.
- 60. Overuse Setup orTeardown (integration test)
- 61. Overuse Arrange (mayneed to refactor)ResourcesBooks“Art of Unit Testing” - Roy Osherove“Test-Driven Development in Microsoft .NET” – James Newkirk“Pragmatic Unit Testing in C# with NUnit” – Andy Hunt, Dave ThomasTesting FrameworksNUnit - http://www.nunit.orgMbUnit - http://www.mbunit.comMocking FrameworksRhino Mocks- http://www.ayende.com/projects/rhino-mocks.aspxMoq - http://code.google.com/p/moqTypeMock - http://site.typemock.comEmail: joe@volaresystems.comOffice: 303-532-5838, ext 101Web: http://VolareSystems.comBlog: http://VolareSystems.com/BlogTwitter: joe_in_denver