What happens when a global outage reveals the cracks in our testing processes?

In this episode of Test Case Scenario, Jason Baum, Titus Fortner, and Marcus Merrell dissect the recent CrowdStrike incident that sent shockwaves across the world. They dive into the incident report, uncovering the key failures and oversights that led to the outage.

You'll learn about the systemic issues in current testing methodologies, questioning whether shift-left testing genuinely enhances software quality or places an unrealistic burden on developers. Through these examples, you’ll hear how small missteps can lead to significant consequences. Tune in to understand the complexities of modern software testing and how to safeguard against major system failures in the future.

Join us as we discuss:
(00:00) Preliminary post-incident review on the global outage
(06:10) Importance of understanding and testing configurations
(11:27) What is shift-left testing and its limitations
(13:52) Differences between unit tests and integration tests
(16:06) Risks of removing QA teams and relying solely on developers
(18:56) Evaluating risk profiles and writing appropriate tests
(19:53) QA's role at the decision-making table
(21:23) Understand the critical risks that can end a company
(22:42) The pitfalls of coverage metrics in QA
(25:03) The hidden dangers of overlooked bugs and incomplete testing

We’d love to hear from you! Share your thoughts in the comments below or at community-hub@saucelabs.com.

SUBSCRIBE and visit us at https://saucelabs.com/community to dig into the power of testing in software development.

Sign up for a free account and start running tests today at https://saucelabs.com/.

• Sauce YouTube channel: / saucelabs
• 💡 LinkedIn: / sauce-labs
• 🐦 X: / saucelabs