Building Operable Software with TDD (but not the way you think)
summary
A credit-lending project uses WebApplicationFactory to run APIs in-memory and replaces thousands of brittle unit tests with outside-in component tests that exercise routing, DI, serialization and persistence from the consumer surface; observability is used as test evidence via open telemetry traces so tests can assert whether cache or database was hit; a custom xUnit open telemetry helper records traces and results are inspected in Honeycomb to debug and compare prod vs local.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:22Defining operable software
- 7:00Rethinking TDD
- 13:35Component testing
- 17:25Outside-in testing
- 26:50Practical testing code
- 36:29What to test
- 43:02Observability and ODD
- 45:02Observability in tests
- 49:06Best practices
- 50:14Conclusion
related talks
52mBuilding Operable Software with TDD (but not the way you think)
52mBuilding Operable Software with TDD (but not the way you think)
01h 02mTesting First - Getting The How
46mHow John Started to Like TDD (Instead of Hating It)
26mUnit tests and TDD does NOT have to be boring
02h 58mOverview of Testing in Our Applications
58mTDD for database related code, how is it possible?
57mAdvanced Testing Techniques: Tips from the trenches