The secret unit testing tools no one ever told you about
summary
Shows concrete tools and practices that cut test maintenance: use a Builder pattern for large test objects to avoid brittle setup, use an AutoMocking container (autofake/autofac style) so constructors add dependencies without rewriting tests, use assert multiple / aggregate-assertion libraries or FluentAssertions to report all failures, adopt BDD/spec frameworks (SpecFlow/Spock) for readable specs, run only affected tests with dotCover/NCrunch/Live Unit Testing to avoid 3,000 tests taking 15 minutes, and try mutation testing to find untested behavior.
AI-written summary · about
chapters (20)
- 0:00Start
- 4:04Unit Testing Framework
- 4:57Mocking Framework
- 7:14J Unit
- 9:56Writing Unit Tests
- 12:26What Is Triple-A
- 16:00Test Setup Test Initialize
- 20:55The Builder Pattern
- 33:06Assertions
- 34:02The Self Helper
- 35:03Assertion Libraries
- 35:51Test Organization
- 37:03Bdd
- 38:57Bdd Framework
- 42:18Test Execution
- 43:15Continuous Tests Tools
- 43:48Live Unit Test
- 47:22Test Structure
- 47:34Continuous Testing
- 51:41Mutation Testing
related talks
47mThe secret unit testing tools no one ever told you about
57mAdvanced Testing Techniques: Tips from the trenches
59m.NET Testing Techniques You Didn’t Know You Needed
01h 05mMicrotesting
43mUnselfish Testing
42mUse testing to Develop Better Software Faster
44mTesting the untestable - patterns and use cases analysis
26mTesting the Tricky Stuff