Building Confidence Together: Continuous Integration & Testing
summary
CI work focuses on concrete changes: move validation into pull requests, run linters and a Python static type checker as pre-commit hooks so failures surface immediately instead of 20–30 minute CI runs, measure build speed and pass rates, and treat flaky tests as technical debt that triggers investigation not reruns. Standardize pipelines across teams, gate integration and deployments on automation, track a cost of quality metric (1400‑employee org example), and automate style and fixable checks so every commit tested actually speeds delivery.
AI-written summary · about
chapters (9)
- 0:00CI and testing introduction
- 1:56CI pipeline failures
- 6:30Better CI and testing practices
- 10:24CI visibility at scale
- 13:16Automated testing role
- 18:59Testing culture
- 24:20Developer resistance to testing
- 28:45CI and testing value
- 31:35Closing remarks
related talks
01h 15mThe Practices That Make Continuous Integration
34mContinuous Integration: A Bittersweet Love Story
45mContinuous Integration: That’s Not What They Meant
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
46mContinuous integration - that's not what they meant
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
38mContinuous Integration May Have Negative Effects
24mCI/CD Best Practices to Deliver Software Faster