Limitations for Playwright
Firefox on macOS 15 (Sequoia)
Firefox is not supported on macOS 15 (Sequoia) due to a known macOS firewall bug that blocks Firefox network connections. Use macOS 14 for Firefox testing on ARM.
Special Characters in Test Names
Test names are validated before execution. The following rules apply:
Allowed characters (no change):
- Letters:
A-Z,a-z - Digits:
0-9 - Dash:
- - Underscore:
_
Replaced characters (automatically converted to -):
+ , @ / % ' \ = ? < > ` # & $ " | : ! ( ) (space) . ; [ ] * { } ~ ^ " " ' ' —
These characters are silently replaced with a dash (-) to prevent errors in report generation.
Disallowed characters (test will fail to start):
- Non-ASCII characters such as
®,™,–,é - Emoji characters
- Any other characters not listed in the allowed or replaced categories above
If your test name contains disallowed characters, the test will be rejected with an error response before execution begins.
Playwright 1.31.1 + Webkit + Sauce-Connect
When using Sauce-Connect, Webkit browser is unable to load any website that is hosted on the Internet. Local websites can still be loaded.
macOS 12 + Playwright 1.44+ + Webkit
Webkit is not working on macOS 12 since Playwright 1.44.0.
macOS 14 + Playwright 1.62+ + Webkit
Webkit is not working on macOS 14 since Playwright 1.62.0. Playwright pins macOS 14 to a frozen WebKit build that the 1.62 library is no longer protocol compatible with. Use macOS 15 for Webkit testing on Apple Silicon.
macOS 12 + Playwright 1.62+ + Chromium
Chromium is not working on macOS 12 since Playwright 1.62.0. Chrome for Testing 151 (bundled with Playwright 1.62) requires macOS 13 or later. Firefox on macOS 12 is unaffected.
macOS 11 + Playwright 1.29+ + Webkit
Webkit is not working on macOS 11 since Playwright 1.29.0.
Playwright HTML Reporter + Trace Viewer
Because of a limitation in how assets are stored on our platform, configuring your tests to use the built-in HTML reporter and Playwright's Trace Viewer feature will not work as expected.
Chrome launchOptions
If you use project specific launchOptions along with setting Chrome as the browser, you'll encounter the following error:
browserType.launch: Chromium distribution 'chrome' is not found at C:\Users\sauce\AppData\Local\Google\Chrome\Application\chrome.exe
This is because playwright's project specific settings override the global configuration that Sauce Labs provides during runtime. In this case, the location of the browser binary. Make sure that launchOptions are not set when running on a Sauce VM.
Webkit + Windows
There is a known issue in Playwright that prevents some sites from loading in Webkit on Windows with the error SSL peer certificate or SSH remote key was not OK. We recommend running your Playwright + Webkit tests on our Mac VMs by setting the platformName to macOS 15.
Tests running through Sauce Tunnels are unaffected.