Systems | Development | Analytics | API | Testing

Explores the financial and reputational impacts of poor API performance, using real-world examples to show how delays and downtime affect businesses.

An overview of the different types of API performance testing (load, stress, spike, etc.), highlighting the core benefits like preventing outages and improving user experience.

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 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.