Navigating Through Test Failures | From Challenges to Solutions
summary
Automated tests are only half the job; the remaining work is five triage steps: get tests to run, filter noise, analyze failures, notify the right teams, and track fixes. Practical moves include test prioritization and multi‑stage runs, test impact analysis using ML to pick relevant tests, containerized or ephemeral environments for reproduction, journaling diagnostic steps, annotating snoozed failures with ticket IDs, and embedding commit hashes in builds so fixes trace cleanly.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:34Understanding test triaging
- 3:18Getting tests to run
- 6:08Filtering test noise
- 9:41Analyzing failures
- 13:16Raising issue awareness
- 15:27Tracking fixes
- 16:51Conclusion and Q&A
related talks
24mHow to solve intermittent issues, aka Random Failures
16mStrategy for Acing Continuous Testing
36mShifting Left: How to Build a Culture of Testing
08mStop the Retries in Tests & Reruns of Failing Test
48mHow to Stop Hating your Tests
37mTransforming Testing from a Task to a Strategic Mindset
55mThe art of living with broken things
55mTop 5 Pain Points of Test Automation