Downloaded 14 times
Uploaded byGil Zilberfeld
Introduction to Unit Testing
This document is a presentation on unit testing that covers: what unit testing is and why it's important; different unit testing frameworks for languages like C++, Java, C#, and JavaScript; techniques for testing legacy code like isolation and mocking; tips for writing unit tests and practicing test-driven development. The presentation emphasizes that unit tests should run quickly, be readable, focused on testing individual units of code, and help enable refactoring of code with confidence.
More Related Content
Similar to Introduction to Unit Testing
More from Gil Zilberfeld
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Introduction to Unit Testing
- 1.
- 2. @gil_zilberfeld Hello! I AM GILZILBERFELD www.gilzilberfeld.com www.everydayunittesting.com @gil_zilberfeld
- 3.
- 4.
- 5. @gil_zilberfeld Manual tests Slow Do notscale Encourage forgetfulness Immoral
- 6. @gil_zilberfeld Automated tests Run allthe time Don’t complain Don’t forget
- 7.
- 8. @gil_zilberfeld Why unit tests? ◉Quick feedback ◉ Confidence to change your code ◉ Quicker than debugging ◉ Knowing your code works ◉ Low TCO ◉ Small setup overhead ◉ It’s not bugs if it’s caught before QA ◉ Go faster
- 9. @gil_zilberfeld xUnit frameworks Test identification Executionand reporting Asserts
- 10. @gil_zilberfeld C++ xUnit frameworks CppUnit BoostTest Catch Google Test
- 11.
- 12.
- 13.
- 14.
- 15. @gil_zilberfeld Make unit testsgreat again! What makes them great?
- 16.
- 17.
- 18. @gil_zilberfeld Refactoring ◉ Changing theform of the code without changing the functionality ◉ Safer with tests ◉ But sometimes we need to refactor in order to test
- 19. @gil_zilberfeld Continuous integration The mindset,not the tools
- 20.
- 21. @gil_zilberfeld Let’s get backto code Legacy code, that is.
- 22. @gil_zilberfeld Legacy code ◉ Containsall kind of dependencies ◉ Does all kinds of things together ◉ It’s ugly ◉ It’s fragile ◉ It’s rotting
- 23. @gil_zilberfeld Legacy code It’s hardto unit test
- 24.
- 25. @gil_zilberfeld Mocking frameworks ◉ Testyour code for different scenarios ◉ Fake the dependencies ◉ Change behavior of methods ◉ Assert method calls
- 26. @gil_zilberfeld C/C++ mocking frameworks GoogleMock Hippo Mocks FFF … and many more
- 27.
- 28.
- 29.
- 30.
- 31.
- 32. @gil_zilberfeld Unit testing advice ◉Think ahead ◉ Make a test plan, not just for unit tests ◉ Test what you’re working on ◉ Unit testing is a team sport ◉ Coverage metrics
- 33. @gil_zilberfeld Unit testing advice ◉Quick feedback ◉ Organize your tests ◉ The cone of dependency ◉ Name like a detective ◉ Readability first
- 34. @gil_zilberfeld Unit testing advice ◉Test one thing ◉ Black box vs white box ◉ Test framework emergence
- 35.
- 36.
- 37.
- 38.
- 39. @gil_zilberfeld Resources ◉ Michael Feathers Workingeffectively with legacy code ◉ “Uncle Bob” Robert Martin Clean code The clean coder ◉ Kent Beck Test driven development by example Extreme programming explained
- 40. @gil_zilberfeld Resources ◉ James Grenning Testdriven development for embedded C ◉ Martin Fowler Refactoring: Improving the design of existing code ◉ James Shore Let’s play TDD
- 41. @gil_zilberfeld Thanks! ANY QUESTIONS? You canfind me at: @gil_zilberfeld http://www.GilZilberfeld.com http://www.EverydayUnitTesting.com