TRIM Your Automated Tests
summary
Introduces a concrete TRIM checklist with code examples and a modeling technique that maps actors to system layers so tests target the lowest risk layer possible, shows how to mock APIs to shrink UI tests, and demonstrates the data builder pattern for fast, reliable setup. Recommends running tests multiple times to detect flakiness, collecting videos logs and headers on failure, pruning legacy tests rather than hoarding them, and optimizing pipelines (examples include 7‑hour runs vs 12‑minute runs) to improve mean time to feedback.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:53Problems with automated testing
- 8:26Introducing TRIMS model
- 10:12Test automation triangle myth
- 13:04Targeted testing via system modeling
- 17:38Reliable and deterministic tests
- 21:55Readable test names
- 25:45Debugging failing tests
- 28:11Clean code for test suites
- 30:57Speed in tests
- 33:23Applying TRIMS to suites
- 34:47Q&A
related talks
51mRedefining test automation
26mKeeping Your Tests Lean
08mStop the Retries in Tests & Reruns of Failing Test
47mEradicate Flaky Tests
57mAdvanced Testing Techniques: Tips from the trenches
44mTesting the untestable - patterns and use cases analysis
44mTechniques to Eradicate Flaky Tests
32mLiving on Crotches or UI Automation Antipatterns
