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.
What is Sauce Testrunner Toolkit?
Sauce Testrunner Toolkit makes setting up, writing, running, and debugging web tests easier and faster for developers during early pipeline testing. It has everything you need to run end-to-end tests. We’ve compiled a container with Chrome and Firefox browsers pre-installed and also includes all types of automation frameworks like Puppeteer and Playwright with support for Cypress coming soon. With a single command, you can execute tests from your laptop and report data to the Sauce Labs public cloud for further analysis. Or if you want to test on more than Chrome and Firefox (ie: mobile), you can run the Sauce Testrunner Toolkit on our platform where the test would be executed close to the virtual machine to speed up test execution.
Why Puppeteer + Jest?
As a Developer, QE, SDET, or Automation Engineer we are all looking for the same thing. We want a solution that is easy to maintain, fast, deterministic, and well adopted. We want the benefit of community and all of the support, improvement, and engagement that goes with it. For years, Selenium and Appium have fit this description. And they still do. But they are not alone. Puppeteer, Playwright, and others have shifted left and are also providing developers the type of magical test experience that QA and QEs find in Selenium and Appium. Today we start with Puppeteer, tomorrow we will add more.
Why Open Source?
How Does it Work?
In the global developer survey by GitLab, testing was identified as one of the key pain points that hasn’t been solved. This is as much because the definition of test has changed as it is that our underlying toolchains have changed dramatically. DevOps, continuous integration, and continuous delivery are no longer unusual terms. We’ve therefore taken a purposefully lightweight, open, approach that you can easily expand on. Let’s dig in.
Use standard Jest and Puppeteer to write your tests. There isn’t a lot to it. Here is an example that simply visits our demo app and verifies the page title is “Swag Labs”:
2. We’ve introduced a new Sauce Labs entity called
saucectl. The new
saucectl is a binary that you can use to run tests locally or to execute tests in an arbitrary Pipeline. The commands are simple such as
saucectl run. By using a single CLI tool you will be able to run your framework of choice preconfigured with Sauce Labs. This eliminates any setup time and lets you focus on writing tests.
3. For those of you using a cloud CI/CD tool, we have a variety of Docker images available to use. Each Docker image contains everything you need to start testing. Just add your Sauce Labs credentials and your CI pipeline is connected to Sauce! Our example repo has both a GitHub Actions workflow template and a CircleCI config template. If you are using something else, don’t worry. Just instantiate the container and execute
saucectl run or download the binary and go from there. Either will work.
4. Navigate to your Sauce Labs account to see not only the test you ran but also the visual output, and your test analytics. Speaking of analytics, now would be a good time to take a look at Failure Analysis too. We designed our new capabilities to automatically link to the AI/ML capabilities, called Failure Analysis, that find common problems across tests from any source. Have a flaky API or test, Failure Analysis can tell you where it is happening regardless of where the test executed - mobile, functional browser, or native pipeline.
5. Actually that’s it. We did a lot more, but those are the keys to getting started.