The secret unit testing tools no one ever told you about
summary
Argues that unit test frameworks only run methods and so the real gains come from using concrete tools and patterns: replace brittle shared setup with Builder pattern factories and auto-mocking containers (demoed with AutoFake/AutoFac to auto-create fake dependencies), collect multiple assertion failures instead of letting the first exception hide others (a custom assert-collector), prefer unit-level BDD names/specs for clarity, and run only impacted tests continuously using NCrunch or Live Unit Testing/dotCover so large suites stay fast and maintainable.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:41About me
- 1:55Why unit testing tools
- 3:25Unit testing framework
- 4:34What is a unit test
- 6:00What a good unit test should be
- 8:54The Triple A
- 10:11Not enough
- 10:22Arrange
- 17:51Setup Letters
- 19:39Factory methods
- 20:36Builder pattern
- 21:23Builder method
- 22:59Automocking
- 24:24How does it work
- 28:06asserts
- 28:31dont use many tests
- 29:10assert protest
- 30:06test form
- 30:42assertion exception
- 33:07JUnit
- 33:50NewUnit
- 34:37What is the difference
- 36:26What can you do
- 37:01SIRT helper
- 38:04Fluent assertion
- 38:51The problem
- 39:30BDD
- 40:36Specflow
- 41:33BDD specification
- 43:25Live unit testing
- 45:38Wrap up
related talks
53mThe secret unit testing tools no one ever told you about
44mTesting the untestable - patterns and use cases analysis
57mAdvanced Testing Techniques: Tips from the trenches
43mUnselfish Testing
55mThe Science of Unit Tests
37mClean Test Code
26mTesting the Tricky Stuff
39mTen things you heard about testing that might be wrong