"What does system design mean to tester?"
summary
Claims that Heisenbugs dominate crashes in mature distributed systems and urges testers to treat architecture as testable evidence. Shows a built video uploader/download system with API gateway + queue + RDBMS/NoSQL and explains tradeoffs: consistency vs availability, eventual consistency, latency, cost. Recommends designing tests for cross-service transactions, lost notifications, data split/reassembly, performance and security impacts, and learning distributed patterns and AWS tools to validate whether the design actually works.
AI-written summary · about
chapters (5)
- 0:00Bug types in testing
- 1:03Heisenbugs and systems
- 2:15System design for testers
- 3:31Applying a testing mindset
- 5:28Key takeaways and conclusion
related talks
46mKeeping system design under control using isolated unit testing
28mDesign for Testability
42mDesign Driven Concepts for Automated Testing
51mTesting Software Architecture
11mThe Importance of Component Testing When Testing Architecturally Complex Systems
09mSystems Thinking for Testers
39mTen things you heard about testing that might be wrong
43mTesting Software Architectures