The missing piece of the continuous integration puzzle
summary
Continuous integration runs orders of magnitude more tests now — thousands per hour — and about 25% of failures remain hard, intermittent and non-deterministic. The demo shows CI storing recording artifacts (megabytes to gigabytes per failure) and using undo LiveRecorder to capture non-deterministic inputs. Teams replay failures with reversible debugging, step backwards to the exact corrupting write (example: cache stores garbage after a loop writes sqrt(-1)), and root-cause and fix flaky, infrastructure or timing bugs much faster.
AI-written summary · about
chapters (4)
related talks
45mRunning Tests in Continuous Integration
34mWhy continuous testing is essential
01h 00mAutomation Engineer’s Way to Continuous Integration
46mContinuous integration - that's not what they meant
01h 15mThe Practices That Make Continuous Integration
32mBuilding Confidence Together: Continuous Integration & Testing
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
35mMassively Continuous Integration: From 3 days to 30 minutes