The Sauce Labs Cookbook

Sauce Headless

Front End Performance Testing


External Resources

More Info

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 CI/CD workflow. 

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 Click command. 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?

  1. Include these desired capabilities for tests that are executed on Sauce Labs:
  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.
  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 Existing Test Scripts

For more information, check out these topics:

  • No labels