Systems | Development | Analytics | API | Testing

When it comes to automation, what you choose to measure can make or break your team’s quality efforts. Focusing too much on one KPI, like automation coverage, can actually hurt the quality of your tests—and vice versa. Before diving into automation, @Chris Wallander suggests a simpler and often overlooked approach. Start with requirements coverage. If you haven’t documented and tested against your requirements, you’re flying blind until something breaks in the real world.

Discover key best practices for testing on the new iOS 18. From reviewing release notes to ensuring compatibility with small-scale rollouts, this video covers a few essential strategies to help your app succeed on the latest platform.

When you push that code, you’re not just releasing software—you’re putting your reputation on the line. Are you proud of what’s going out the door? @Chris Wallander from @Taxwell throws down a challenge: Quality isn’t just for the QA team—it’s on all of us. Whether you're coding, testing, or managing, if you see something off, speak up. Silence doesn’t fix bugs. But here’s the real question: Is your team talking about quality? And if not, what’s stopping them?

Ready to future-proof your apps? With the iPhone 16 and iOS 18 here, testing on these new OS and devices is critical. Let’s dive into why?

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.