Systems | Development | Analytics | API | Testing

At Sauce Labs, we define Continuous Testing as a “best practice approach to software quality that involves testing earlier and more often throughout the development lifecycle.” Teams that adopt continuous testing realize a number of benefits, including fewer bugs found in production, faster release cycles, and overall improved customer experience. Another rarely discussed benefit is that as the number of quality checkpoints increases, so does the volume of test data and quality signals.

In Web UI testing, testers have to deal with increasing new page objects and changing identifiers when the web application grows. No matter if you are a manual or an automation tester, updating object locators for the Application Under Test (AUT) is a required step when changes are made. This helps ensure regression testing flows without friction and all key functionalities are not affected.

Earlier this year, Sauce Labs announced the release of our newest product to expand developer-first capabilities: Sauce Testrunner Toolkit. Currently in a free beta, it makes setting up, writing, and running web tests easier and faster for developers during early pipeline testing. This is the first in a number of updates to our platform that empower developers with the tools they need to achieve quality at scale.

Test automation helps increase development speed while reducing cost and effort. In this article, we will share how to automate testing to help keep a test automation initiative on the right track with key tips for test execution, design and maintenance for large enterprise applications.

So you’ve realized the benefits of test automation. Through your own research, or perhaps a small proof of concept, you’ve realized removing once-manual quality processes can accelerate release cycles and improve your user experience. You’ve built a small suite of tests, and the benefits are real. The next step in your journey, you realize, is to achieve the real value of automation, which means running it continuously and at scale.

OctoPerf’s report engine provides many graphs to sort and presents test metrics in a comprehensive way. We’ve tried to improve it over the years so that you can access critical information very quickly. But requirements vary from one project to the other. In this post we will look at how you can configure the report to show you preferred metrics, and also all the shortcuts you can take to achieve this goal.

You may have spent a considerable amount of time configuring Postman requests for your in-house API tests, and you wish to use them without having to create them again from scratch on Octoperf. That’s one of the many situations where Octoperf’s compatibility with Jmeter is going to come in a handy.