Over the years software tools, testing frameworks, and development practices have evolved to meet new challenges. This shift means testing is happening earlier in the software development lifecycle with developers increasingly taking on more responsibility for testing with a focus on speed. That’s why we’re excited to announce the expansion of our developer-first test capabilities.

A little more than a year ago today, aiming to address what we saw as a significant gap in the testing market, we first launched the Sauce Labs Continuous Testing Benchmark, a new report organizations could use to see how their continuous testing efforts stacked up against both critical best practices and the testing efforts of other enterprises.

Like many things in life, the toughest part of a test automation project can be getting started. That's why the Solution Architects and Information Developers are working hard to produce good materials for anyone getting started with test automation and Sauce Labs. To help this effort, we've reworked some Python example code, which can be found in the Sauce Labs Training Demo Python repository.

In these unprecedented times, everyday life has begun to change in ways we couldn’t even dream of only a few weeks ago. With the global population moving to more isolated lifestyles (remote working policies, social distancing, etc.) people are looking to digital services to help create a sense of calm and normalcy.

If you work in QA, you're probably accustomed to thinking of software monitoring as someone else's job. Traditionally, responsibility for monitoring applications fell to IT teams; QA's role ended with pre-deployment testing, and QA engineers did not usually touch monitoring tools. But the reality is that monitoring tools—meaning tools designed to help track application availability and performance, and also alert teams to problems—aren't just for IT teams.