Testing the untestable - patterns and use cases analysis
summary
Advocates pragmatic, measurable testing rules favoring fast “gray‑zone” tests that run full integration checks in under 30 seconds (ideally <10s). Recommends using simple in‑memory fake repositories instead of heavy mocking, isolating external systems behind ports, and tools like a Timeflow library to freeze/fast‑forward time, Testcontainers for queues, sampling/listening instead of long sleeps, and agent adapters to reuse the same acceptance tests across unit/integration/UI; reports reducing build time from 12 to 5 minutes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:33Untestable test gray area
- 7:0730s integration tests
- 9:55Library testing constraints
- 12:46Isolating dependencies
- 17:42Fakes vs mocks stubs
- 22:46Reusable tests across levels
- 29:28Time-dependent apps testing
- 34:42Async systems queues
- 41:05Testing principles cohesion
- 44:41Test strategy from start
- 45:45Summary Q&A
related talks
44mTesting the untestable - patterns and use cases analysis
44mTesting: Integration Tests - The good, bad and ugly
57mAdvanced Testing Techniques: Tips from the trenches
45mTesting the untestable PART II – patterns, use cases and practices
40mIntegration Testing from the Trenches - Rebooted
37mUnderstanding the successes and the pain points of different testing strategies
41mPragmatic Testing
01h 07mProperties of Unit Tests