Testing First - Getting The How
summary
Shows a pragmatic path to testing-first by building a .NET Web API with xUnit, an in-memory repository and WebApplicationFactory tests that exercise inputs and outputs rather than internals, uses microspikes and a small “making app” to iterate fast, implements POST/PUT/DELETE endpoints and adds a 409 conflict for duplicate posts, refactors storage from list to dictionary without breaking tests, and warns that tools like SonarCloud 100% coverage can mask problems (one real case passes after 80% of code removed).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:36Testing misconceptions
- 3:04Ignoring functional tests
- 8:20Confirmation bias in testing
- 11:08Start with the problem
- 13:37Collaborate with testers
- 16:04Technical testing strategies
- 17:55Micros spikes for ideas
- 20:23Simplify testing with apps
- 22:51Avoid over-mocking
- 24:41Test APIs outside-in
- 27:13Live demo setup
- 31:53First test for to-do app
- 36:48Build to-do API test-by-test
- 45:51Add duplicate validation
- 48:18Refactor safely with tests
- 50:30Benefits of testing-first
- 52:38Avoid over-abstraction
- 55:11Balance DRY in tests
- 58:21Real-world testing-first
- 1:00:10Testing-first journey
related talks
45mTesting Your Web Apps
41mTesting .NET Web APIs from A to Z
51mFallacies of Unit Testing
56mBuilding Operable Software with TDD (but not the way you think)
52mBuilding Operable Software with TDD (but not the way you think)
52mBuilding Operable Software with TDD (but not the way you think)
50mCreate Web APIs with ASP.NET Core Using Outside In TDD
01h 05mMicrotesting
