AI isn’t going to replace software engineers. @David Morgenthaler explains that while AI might change the landscape, it’s about augmentation, not replacement. Here’s why: Learn more about the future of AI in software development in the full episode of Test Case Scenario.

"Push on green" isn’t about rushing code to production—it’s about smart automation. @David Morgenthaler breaks down how @Indeed balances automation with the need for human oversight: Watch the latest episode of Test Case Scenario to understand why automation and human expertise have to go hand-in-hand for quality software development.

Is speed more important than quality in software development? While getting products to market quickly is tempting, cutting corners on quality can lead to costly bugs and system failures that may result in a large-scale failure and damage your reputation. The real solution? Investing in more QA professionals to ensure your software is both fast and flawless. QA is not just about finding bugs; it's about ensuring the overall health and success of a software project.

Hosted By: Joe Colantonio, Founder, Test Guild Mac Clark, Senior Solutions Engineer, Sauce Labs Gabe Kaufman, Product Marketing Manager, Sauce Labs Background: Engineering efficiency has never been more important for keeping quality high, increasing time-to-value, and ultimately scale. In this session, we will explore how engineering efficiency plays into a continuous quality strategy while also optimizing CI/CD pipelines.

Shifting left to put more on developers? They you have to find the right balance between automation and simplicity. Otherwise, you'll end up with complexity that slows everything down instead of speeding it up. @David Morgenthaler says tools like static analysis and AI-driven tests are shaping the future of software quality: Watch the latest episode of Test Case Scenario to explore how automation can streamline processes without overcomplicating development. It’s working for @Indeed.

What does it really mean to shift left, and are we overburdening our developers in the process? In this episode, Jason Baum, Marcus Merrell, and Evelyn Coleman sit down with David Morgenthaler, a Software Engineering Manager at Indeed, to explore the real-world implications of shift-left testing. Together, they dissect the challenges of integrating continuous quality into CI/CD workflows and the potential pitfalls of placing more responsibility on developers' shoulders.

57% of consumers are willing to switch to a competitor after three or four negative interactions. And that's being generous—sometimes it only takes one or two. Companies can’t afford to ignore red alerts anymore. Take Amazon's checkout flow, for example. It always works because they prioritize testing it rigorously to ensure their core business can generate revenue, even if other features are less polished.

In the last decade, we've leaned heavily on VC-backed tools like @Sumo Logic and @Splunk to help us sift through endless data and logs. These tools are invaluable, but now we're drowning in data, making it tough to focus on what truly matters. This challenge is no different in software testing. Here, many face the dilemma of running thousands of tests nightly with hundreds failing. It’s a sea of alerts and noise, leaving us questioning what we're actually testing.