A second look at Unit Testing with Roy Osherove at Microsoft Swit
Download as PPTX, PDF6 likes1,483 views
The document discusses isolation frameworks for unit testing, including constrained vs unconstrained frameworks and principles for good isolation frameworks. It also mentions faking deep legacy code, six influence forces that impact builds, and creating beautiful builds.
A second look at Unit Testing with Roy Osherove at Microsoft Swit
- 3. • Unit Of Work • Setup Methods • Constrained vs. Unconstrained Isolation Frameworks • Principles of Good Isolation Frameworks • Faking Deep Legacy is OK • Six Influence Forces • Beautiful Builds
- 6. Production Code Unit Of Work Return Value/Exception Noticeable State Change 3rd Party call Public API Test
- 9. Production Code Unit Of Work Noticeable State Change Test Public API Assert
- 12. Production Code Unit Of Work 3rd Party call Test Public API 3rd Party Unit Of Work
- 13. Production Code Unit Of Work 3rd Party call Test Public API 3rd Party Unit Of Work
- 20. Recursive is not explicit: Person.Manager.Manager is already a fake instance without asking for it Chained Expectations are explicit Mock.Arrange(() => Person.Manager.Manager) .Returns(fakeManager)
- 32. Old code
- 44. Extract Scrip
- 45. Build Chain Triggers Triggered by checkin Triggered by end of previo Manual Manual Build Chaining
- 46. • Unit Of Work • Setup Methods • Constrained vs. Unconstrained Isolation Frameworks • Principles of Good Isolation Frameworks • Faking Deep Legacy is OK • Six Influence Forces • Beautiful Builds