Intentional and Unintentional Compromises in Test Automation
summary
Jenkins git plug-in lives on 300,000 installations yet spends 15 months with no tests initially, revealing a claim that some projects ship without tests because the code may be throwaway. Running every commit proves expensive when test suites use 200 parallel containers taking 5–30 minutes each; costs and cloud bills drive choices to skip or discard tests. Flaky tests and a command‑line git security change that tests never exercised show false confidence; tools like Clover and services such as Launchable aim to reduce the test surface.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:40Intentional Choices
- 4:31What We Test
- 9:57Test Value
- 11:31Software Testing Pyramid
- 12:19Software Testing Honeycomb
- 14:11Initial Development
- 15:04Ongoing Care
- 17:52Unintentional compromises
- 18:15Untrained users
- 18:46Unintended compromises
- 19:33Behavioral inertia
- 20:42Your choices
- 21:06Skip tests
- 30:01Fun lead question
- 30:16Chaos engineering theories
- 30:46Confident rollback
related talks
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
35mMassively Continuous Integration: From 3 days to 30 minutes
24mA Comedy of Errors
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
49mHow to Optimize Automated Testing with Everyone's Favorite Butler
39mTrust Issues With UI Automation
37mUnderstanding the successes and the pain points of different testing strategies
28mThe State of Art in Tackling Flaky Tests