Skip to main content

Playwright Advanced Configuring

Environment Variable Expansion

All values in your saucectl configuration support environment variable expansion. $var in config.yml will be replaced according to your shell's environment variables. References to undefined variables will be replaced with an empty string.

Predefined Environment Variables

The following environment variables are available during test execution.

Environment VariableDescription
SAUCE_ARTIFACTS_DIRECTORYAbsolute path to the artifacts directory. Files placed in this folder are persisted with the Job.

Tailoring Your Test File Bundle

The saucectl command line bundles your root directory (rootDir parameter of config.yml) and transmits it to the Sauce Labs cloud, then unpacks the bundle and runs the tests. This functionality is partly what allows Sauce Control to operate in a framework-agnostic capacity. However, you can and should manage the inclusion and exclusion of files that get bundled to optimize performance and ensure security.

Excluding Files from the Bundle

The .sauceignore file allows you to designate certain files to be excluded from bundling.

Add any files that are not direct test dependencies to .sauceignore to reduce the size of your bundle, improve test speed, and protect sensitive information.

Examples of what can be included in .sauceignore:

# .sauceignore

# Ignore node_modules

# Ignore all log files

# Ignore executables/binaries

# Ignore media files

# Ignore documentation

# Ignore sensitive data

Sometimes it's easier to do the inverse: Including files for the bundle.

# Ignore all files by default.

# Re-include files we selectively want as part of the payload by prefixing the lines with '!'.

# Since the whole '/cypress' folder is now included, this would also include any
# subdirectories that potentially contain auto-generated test artifacts from
# the local dev environment.
# It'd be wasteful to include them in the payload, so let's ignore those subfolders.

Including Node Dependencies

The default .sauceignore file lists node_modules/ so locally installed node dependencies are excluded from the bundle. If your tests require node dependencies to run, you can either:

Remove "node_modules" from .sauceignore

Delete or comment out node_modules/ in your .sauceignore file to bundle your node dependencies. For example,

# Do NOT exclude node_modules from bundle
# node_modules/

Node dependencies can increase your bundle by potentially hundreds of megabytes, so consider including only the required dependencies rather than the entire node_modules directory. The following sections provide some methods for limiting the scope of dependencies you must include.

Install "devDependencies" Only

Consider only installing NPM devDependencies if your tests do not require all prod dependencies.

# Only install dev dependencies
npm install --only=dev

saucectl run

Uninstall Nonessential Dependencies

If your standard install includes dependencies that aren't needed to run your tests, uninstall them prior to bundling.

# Install node dependencies
npm ci # or "npm install"

# Remove unneeded dependencies
npm uninstall appium
npm uninstall express

saucectl run

Install Essential Dependencies Individually

If you know that your tests require only specific dependencies, install them individually instead of running npm install or npm ci.

# Install individual dependencies
npm install playwright-xpath

saucectl run

Set NPM Packages in config.yml

You can avoid installing or uninstalling dependencies prior to each bundling operation by defining a default set of NPM packages to install in your sauce configuration file using the npm parameter, as shown in the following example:

- url:
"lodash": "4.17.20"

Alternatively, you can let saucectl selectively include already installed dependencies from the node_modules folder.

- lodash

This feature is highly experimental.

Attaching Test Assets

Any test assets created by your tests at runtime (such as logs, screenshots or reports) you wish to retain along with your test results must be placed in the __assets__ directory of your project root folder. On Sauce Labs VMs, this path is relative to the current working directory.

Nested Paths

Nested assets are stored flat in Sauce Labs. A test asset like __assets__/mylogs/log.txt would therefore be stored and available for download as log.txt. Please keep that in mind when creating custom assets, as examples like __assets__/mylogs/log.txt and __assets__/myotherlogs/log.txt would eventually collide when persisted.

Setting up a Proxy

If you need to go through a proxy server, you can set it through the following variables:

  • HTTP_PROXY: Proxy to use to access HTTP websites
  • HTTPS_PROXY: Proxy to use to access HTTPS websites

Filtering Tests

Playwright supports filtering tests using the grep and grepInvert options.


By default, playwright on Sauce Labs runs with these preconfigured reporters:

If you have a custom reporter, simply set it in your playwright.config.js/ts file:

const config: PlaywrightTestConfig = {
reporter: [

Your reporter runs automatically alongside our reporters. We do not filter out duplicate reporters, which also means that if you already have a list reporter set, you'd see twice the output.

If you'd like a different set of reporters when running on Sauce versus local, check the env variable SAUCE_VM. In the following example, if SAUCE_VM is set (which it will be when running on a Sauce Labs VM), then fancy.reporter.ts is used, otherwise just the built-in list reporter.

const config: PlaywrightTestConfig = {
reporter: process.env.SAUCE_VM ? [
] : 'list',

A limitation on Sauce Labs exists with playwright 1.27.1 or below, where the user defined reporter is only honored when defined as an array: reporter: [['./fancy.reporter.ts']]. Using a string like reporter: './fancy.reporter.ts' would therefore always be ignored.


You can use Playwright to test your app on any browser and emulate a real device such as a mobile phone or tablet. See the Playwright docs for more details.


Playwright is not a real Emulator or Simulator. It just emulates the browser behavior such as userAgent, screenSize, viewport and etc.


To get trackable screenshots in Sauce Cloud, please refer to the Playwright Screenshot documentation and implement the following code snippet:

test('take a screenshot', async ({ page }, testInfo) => {
await page.goto('');
await page.screenshot({ path: 'screen_capture_unique_name.png' });
await testInfo.attach('screen_capture_unique_name.png', { path: 'screen_capture_unique_name.png', contentType: 'image/png' });

The captured screenshot will be logged in `sauce-test-report.json`` and can be accessed in the "Screenshots" tab on the Sauce Labs web UI. You can also download the screenshots as artifacts.


Please be aware that using the default screenshot setting in the Playwright Config may result in potential issues on Sauce Labs. By default, Playwright generates screenshot files in the following structure:


However, Sauce Labs only supports a flat file hiearchy, which means that test-finished-1.png would be uploaded and overwritten, since only one file named test-finished-1.png can be stored.