Office Hours: Tackling Flaky Tests Are flaky tests wreaking havoc on your CI/CD pipeline? Watch this pre-recorded presentation from our Sauce Labs Community Office Hours, where Titus Fortner, Developer Advocate, shares strategies for identifying and resolving flaky tests. Learn the best practices to make your tests more reliable and ensure your automation runs smoothly every time.

Ever feel like you’re wasting energy on endless automation tests that just don’t cut it? @Veronika Takmazyan recommends focusing on stability and quality right from the start. If you invest in quality early on, you’ll avoid the headaches of fixing bugs and rewriting code later. Deliver once, deliver well, and move on to the next big thing. If you’re wondering how to get your team on board with this mindset, Veronika sums it up perfectly.

In this video, we dive into a few key strategies for testing on the latest device models, to ensure your app stays cutting-edge and performs seamlessly on the newest platforms.

In software development, it doesn’t matter who found the bug or who’s responsible for fixing it. What matters is that the product works. @Veronika Takmazyan shares a real-world example from their team’s work on a @Salesforce hybrid app, where ownership and collaboration are essential. Whether it’s web views or native elements, the goal is clear: deliver quality at every step, no excuses. Watch the latest episode of Test Case Scenario to learn more about how embracing responsibility across teams ensures that quality isn’t just an afterthought—it’s built into every release.

Transform the way you identify and resolve issues across the software development lifecycle. Learn how Sauce Labs Error Reporting and Insights advanced filtering and grouping can help you to find and resolve failures in your test suite and errors in production faster! Reduce toil and allow engineering teams to focus on innovation while ensuring efficiency across both testing and production phases. Identify Root Causes Faster: Streamline root cause analysis, allowing your team to quickly address the most pervasive issues and reduce the burden on engineers.

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.

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.

Ever thought about the power of glanceable and audible information? One team used a pattern of white noise—crickets—to indicate their site's status. When something went wrong, the crickets stopped, and everyone immediately knew to take action. It’s a brilliant way to process information passively and focus on what truly matters. Check out the most recent episode of Test Case Scenario as we discuss how to cut through the noise and highlight what’s truly important.

Office Hours: Optimizing Test Execution Speed Are slow tests slowing you down? Watch this pre-recorded presentation from our Sauce Community Office Hours session where Diego Molina, Developer Advocate, dives into the best practices for optimizing test execution speed!

Drowning in notifications? Prioritize what truly matters. @Marcus Merrell asked himself, "Will I stop for any alert from this app?" Only three made the cut. Apply this to software testing: "Will we stop the shipment if this test fails?" If not, that test isn't helping. Don’t be afraid to delete unnecessary code. Quality control and assurance are crucial.

(Struggling to keep up with the relentless stream of notifications? You're not alone. In this episode of Test Case Scenario, Jason Baum and Marcus Merrell explore the impact of alert fatigue and signal overload on productivity and quality.