The test execution engine can be selected from two options: Selenium and Playwright, but for organizations created on or after 2026/8/24, Playwright is set as the default because it is expected to improve execution speed and stability.
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
Considerations When Migrating from Selenium
When migrating existing Selenium tests to Playwright, keep the following points in mind:
- Selenium and Playwright differ in execution speed, operation timing, and other behaviors. As a result, tests that run successfully with Selenium may require adjustments to their test steps when run with Playwright.
- Unknown issues may occur when using Playwright.
Therefore, rather than migrating all tests to Playwright at once, we recommend gradually migrating tests to Playwright while continuing to run your existing tests with Selenium.
For example, you can migrate your tests as follows:
- Continue running your tests with Selenium while also running some of them with Playwright.
- Review the Playwright test results and adjust the test steps as necessary. If you encounter an issue that seems to be caused by MagicPod, please contact MagicPod Customer Support.
- Once you have confirmed that tests run successfully with Playwright, gradually migrate those tests to Playwright.
If you encounter any issues during the migration, switch back to running the affected tests with Selenium as necessary. Once the issues have been resolved, resume the migration to 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 in both cloud and local environments (including batch run)
※When using Playwright in your local environment, please install MagicPod Desktop version 1.67.0 or later. (Download the latest version here)
- Batch run with Chrome on BrowserStack
Execution on browsers other than Chrome (such as Edge or Firefox) is not currently supported.
Limitations in Test Commands
The following commands have limitations, so caution is required when using them.
-
Input keyboard key command
There is no distinction between
EnterandReturn; both are executed asReturn. -
Assert there is no visual diff command
If you use a baseline image from a test result executed with Selenium as the expected image, an image difference will be detected when the test is executed with Playwright.
-
Click command
If the target UI element is in a "disabled" state, a timeout error will occur. (This does not occur when running tests with Selenium.)