The test execution engine uses Selenium by default, but can be changed to Playwright if needed. Playwright can be used to improve execution speed and stability, depending on the test case.
This section explains how to use Playwright to execute tests and the important points to note when using Playwright.
This feature is available to users subscribed to the following plans:
- Enterprise Plan
- New Standard Plan 2025 (Refs)
Table of Contents
How to use Playwright
To execute tests using Playwright, configure the settings as follows in the Advanced Settings tab of the Batch Execution Settings dialog:
- Playwright: Use
Important notes when using Playwright
When using Playwright, please note the following:
- If the Assert there is no visual diff command uses images from test results that were executed without Playwright, visual differences will always occur when the test is executed with Playwright.
Limitations
Limitations in the Execution Environment
Currently, Playwright can be used under the following environments and conditions:
- Creation and execution of test cases using Chrome Cloud browser (including batch run)
Execution on a local PC and execution on browsers other than Chrome (such as Edge or Firefox) are not currently supported.
Limitations in Test Execution Settings
If any of the following features are enabled in the test execution settings, Playwright test execution will automatically be turned off—even if Playwright is set to be used and the test will be executed without Playwright:
- Mobile Emulation
- Client Certificates
- Chrome Extensions
Limitations in Test Commands
The following commands have limitations, so caution is required when using them.
- There is no distinction between
EnterandReturn; both are executed asReturn.