Continuous testing isn't just about automation—it's about strategy, feedback, and getting your team unstuck. In today’s episode, Jason Baum and Marcus Merrell are joined by former co-host, Evelyn Coleman, to welcome Marc Hornbeek on the show. If you’re not familiar with Marc, he’s a legend in the world of DevOps. The author of “Continuous Testing, Quality Security and Feedback,” and CEO and Principal Consultant of Engineering DevOps Consulting, he knows what it takes to succeed in the industry.

Hosted By: What is the impact of development velocity? One of the leading financial services companies reduced test execution time from 6 days to 36 hours, equating to 4x time savings. The pressure to innovate quickly and keep up with competitors is real. Watch Marc Hornbeek, CEO of Engineering DevOps Consulting and author of Engineering DevOps, and Marcus Merrell, Principal Technical Advisor at Sauce Labs, for a discussion on innovation velocity and to learn how DevOps teams are iterating quickly so they can focus on delivering innovative software.

Hosted By: Rachael Yomtoob, Product Owner - axe DevTools Mobile, Deque Marcus Merrell, Principal Technical Advisor, Sauce Labs Jason Baum, Senior Director, Developer Marketing. Sauce Labs Background: The European Accessibility Act (EAA), a law that defines accessibility requirements, takes effect on June 28, 2025. According to the EU, EAA will make life easier for the roughly 87 million people living with disabilities–almost one in five Europeans. Seen by many as a landmark law, the time to meet compliance is running out.

Balancing speed and quality isn’t just about product development—it’s about shaping the future of your business. @Evelyn Coleman shares why the limitations on development speed are actually a blessing. Moving too fast without gathering feedback can send your product down the wrong path. It’s the balance between velocity and quality that helps teams gather the insights they need to build something truly impactful.

Is it better to launch fast or wait for perfection? @Saurabh Shanbhag explains the "fail fast" strategy, where teams quickly release imperfect products to get real customer feedback and improve. Instead of taking years to perfect, they launch in months, see what works, and adjust from there. This approach helps companies adapt, find market fit, and build better products based on actual user insights.

Can engineers ever guarantee that nothing will break? @Saurabh Shanbhag explains why unexpected failures are always possible in today’s interconnected tech world. The key is to control what you can and collaborate to build resilient systems. Here’s how to approach it: Watch this episode of Test Case Scenario to learn more about building reliable systems.

Explore how the Sauce Labs and Deque integration empowers you to achieve digital inclusion and ensure compliance with accessibility standards.

Is catching bugs before production really possible? @Saurabh Shanbhag from @DoorDash shares insights on how minimizing bugs is a team effort and not just the responsibility of engineers or QA testers. Collaboration across roles is key to ensuring product reliability. Here’s how teams can prevent issues before launch: Watch this episode of Test Case Scenario to learn more about bug prevention strategies that actually work.

How do you ensure your software system is reliable from design to deployment? In this episode of Test Case Scenario, Jason Baum and Evelyn Coleman sit down with Saurabh Shanbhag, Software Engineer at DoorDash, to discuss the best approaches for preventing bugs and building reliable systems. Saurabh draws on his experience from Amazon, Uber, and DoorDash to explain how teams can focus on strong initial design, thorough testing, and smart monitoring to keep systems running smoothly.

Your partners can make or break critical moments. @Marcus Merrell shares a story about a Black Friday mishap that cost $200,000 due to a partner’s system failure. Customers faced errors with no clear alternatives, leaving them frustrated and the business scrambling. It raises an important question: Are you prepared for when things go wrong, or are you leaving your users stranded without options? It’s not just about the tech—it’s about how you build trust and ensure your users feel supported, no matter what.