DEVOPS DAYS MTL 2018 - Catherine Proulx
summary
Argues for a pragmatic test-first repair of unstable code: don’t stop everything or rewrite, instead test what failed—write the smallest test for each bug fixed, run it even with a cron-job CI and any test runner—and then test what’s going to fail by targeting the ugly modules that keep people awake. Warns against chasing coverage numbers, using brittle canary tests that cry wolf, or replacing skilled exploratory manual testers; culture and incremental wins buy budget and stability.
AI-written summary · about
chapters (10)
- 0:00Legacy code struggles
- 1:51Defining legacy code
- 3:16Recipe for legacy code
- 4:43Testing failures
- 8:00Testing legacy pitfalls
- 10:30Canary testing challenges
- 12:40Manual vs automated testing
- 14:49Culture in legacy work
- 16:35Why legacy code is not inherently bad
- 18:01Building good code legacy
related talks
42mUse testing to Develop Better Software Faster
06mLightning Talk: Automated Testing Done Right
37mSensible Testing
59mAgainst a Harmful Divide: Testing as the Lifeblood of Development
15mTransforming Testing: The Power of TestOps
32mThinking in tests
41mMartijn Goossens: Be a Better Test Friend to Your Team
01h 01mBack to Basics: Debugging and Testing in C++ Software Development