Skip to end of metadata
Go to start of metadata

Enterprise Plans Only

This feature is available for Enterprise plans only. For more information about other benefits that are included with Enterprise plans, check out our Pricing page.

Chrome Only

This feature is available only for testing web applications with the Google Chrome browser.

Why Use Sauce Performance?

Front End Performance Testing is essential in a world where your users demand fast and consistent interaction with your application, and where applications using JavaScript frameworks shift more of the processing work from server-side systems to the browsers themselves. While many development teams will delay user experience testing until the end of their development cycle, or focus only on load/stress testing of their server systems, Sauce Labs offers a front end performance testing tool that you can use to get fast feedback on your web application during the development cycle, and that can be incorporated into your existing CI/CD workflow. Note: for your convenience, you can also try this feature out during your two week free-trial.

How Does Front End Performance Testing Work?

Once the feature is enabled for your organization, Sauce Labs will begin collecting the performance metrics for URLs that were visited during the test execution process and start establishing historical performance baselines for each navigation via a POST URL or a Page Transition. Once the baselines are established, you can incorporate a custom Sauce Labs command into your test scripts to begin generating metrics measured against these baselines. In addition to these metrics, you can also access filmstrips of the page load process and a complete tracing log alongside a set of core user experience metrics.

How Do I Get Started with Sauce Performance?

Choose the workflow that suits you best:

Run your First Performance Tests From the Command Line

Run your first test using our CLI tool (Speedo). Once installed you can quickly call it to run your performance test and it will automatically run jobs on our platforms, sets baselines and checks the metrics for regressions. 

1) Install the package on your system and will make the command available.

$ npm install speedo -g

2) The following examples assume that you have SAUCE_USERNAME and SAUCE_ACCESS_KEY exposed in your environment.

If not you can pass them in as command line parameters -u <username> and -k <access key> or export them via:

$ export SAUCE_USERNAME=Slavocado
$ export SAUCE_ACCESS_KEY=XXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

The simplest way to make use of the Sauce Performance feature is to use the Speedo run command. It accepts the URL of the web page you want to check performance for as parameter and takes care of everything required along the way.

3) Run your first test

$ speedo run <URL>

Capture Performance for Existing WebDriver Tests

  1. Include these desired capabilities for tests that are executed on Sauce Labs:
    ExtendedDebugging:true 
    capturePerformance:true
  2. Run tests against the latest versions of Google Chrome.
  3. Once the jobs are complete, you should see a Performance Tab on the Test Details page with the new performance data.
  4. (Optional) Embed a performance check directly in your functional test by using our custom WebDriver command, as described in Incorporating Front End Performance Testing into WebDriver Test Scripts


For more information, check out these topics:


  • No labels