How to test self-contained Systems
summary
Argues that the right decomposition is self-contained systems — each an autonomous web app that does not share business code or databases — because replacing a monolith with 20+ tiny services often yields a worse distributed monolith. Demonstrates testing tiers with a tic‑tac‑toe example: manual HTTP calls with the command‑line tool HTTP (httpie), automated end‑to‑end via real HTTP, faster edge‑to‑edge by instantiating the app in PHPUnit, and isolated unit tests for game rules so failures pinpoint the fault.
AI-written summary · about
chapters (11)
- 0:00Start
- 22:44Manual Test
- 23:09End-to-End Test
- 25:04Functional Test
- 26:33Dynamic Test
- 27:13Automated Test
- 27:27System Test
- 30:41Edge-to-Edge Test
- 35:41Unit Test
- 37:00Executable Documentation
- 37:17Executable Specification
related talks
57mBuilding Systems that are #neverdone
25mTestable Architecture: Keep 'em Separated
21mUnit Testing Deconstructed
47mSay Goodbye to Microservices, Say Hello to Self-Contained Systems
21mTestable Architecture: Keep 'em Separated
46mKeeping system design under control using isolated unit testing
57mHow I sliced your app
43mWhen testing makes no sense