How Not to Cause the Next Global Outage

Test Case Scenario

Skipping thorough testing? Here's why it's a risk you can't afford to take. On July 19, the world experienced what would be the largest tech outage worldwide. If you’re a software developer or tester, you've likely faced the frustration of a system failing right when it’s most critical. Did you know the complexity of today’s software is a significant reason behind these issues? It’s not just an occasional problem; it's a global challenge.
Our latest episode dives deep with Nikolay Advolodkin, Jason Baum, and Marcus Merrell as they explore a major software outage that recently disrupted industries worldwide. This episode is packed with practical insights and real-world examples of how to prevent such disasters, emphasizing the critical role of quality assurance and testing processes.

Join us as we discuss:
00:00 CrowdStrike’s global software outage
05:59 Kernel update’s irreparable damage
12:42 Basic testing strategy is essential for successful software
16:27 Top five ways to avoid being the next global outage causer
16:42 Gradual software release for low-risk opt-ins
17:55 Integration testing failures and their impact
20:00 Preventing critical failures with proper version control and code quality
21:29 The importance of cross-platform testing and prioritizing releases
23:12 Understanding software dependencies and potential vulnerabilities
24:48 Quality control slipping, apathy increasing, teams eliminated
We’d love to hear from you! Share your thoughts in the comments below or at [e-mail].
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