Use Microsoft Edge in Leapwork Play to record browser actions and run web tests in Play’s managed cloud browser. You can choose Edge for an interactive Preview session or configure a run list to execute its tests in Edge. Google Chromium remains available.
Before you start
-
Open the test case or run list you want to use. Confirm the application URL, test account, and starting data before you record or execute actions.
-
Use the cloud browser provided by Play. You do not need to install a local recorder to follow this workflow.
-
Choose a geographic region available to your workspace. East US access depends on the workspace’s plan or Geographic Region add-on. An unavailable region is not enabled by choosing Edge.
-
If you use MCP, connect your client to Play using the relevant MCP integration guide.
Connect an Edge browser for Preview
-
Open your test case’s browser tab.
-
Select Microsoft Edge in Browser type.
-
Select an available geographic region.
-
Select Connect.
-
Wait for the Edge browser session to connect before you interact with the application.
To change an existing connected session to Edge, disconnect it first, select Microsoft Edge, and connect again. Check the application state before repeating any actions that create or change data.
Record and run a test in Edge
-
Connect an Edge session using the steps above.
-
Select Record.
-
Perform the actions you want to include in the test.
-
Stop recording when you have completed the workflow.
-
Review the recorded steps and expected outcomes.
-
Execute the test in the connected Edge session.
-
Review the execution result and investigate any failed step.
You can also connect Edge manually before generating a test case from a blueprint. The resulting browser workflow can use the already connected Edge session.
A test that passes in Google Chromium still needs to be checked in Microsoft Edge. Browser support does not guarantee that every application, locator, or file-handling workflow behaves identically across both browsers.
Use an existing Edge session with Play Chat or MCP
Connect Edge manually before asking Play Chat or your connected MCP client to record or execute a test in that Preview session.
-
Open the relevant test case in Play.
-
Select Microsoft Edge in Browser type.
-
Select Connect and wait for the session to be ready.
-
Use Play Chat or your connected MCP client to record or execute the intended test in the open session.
-
Review the generated steps and execution result in Play.
This workflow uses an Edge browser you have already opened.
Launch Edge through Chat and MCP
Play Chat and the web automation engine can start an Edge browser and use it for automation. You can use this workflow through Play Chat or your connected MCP client.
Choose Edge for a run list
A run list has its own browser selection. Check it separately from the browser selected for an interactive Preview session.
-
Open the run list you want to execute.
-
Open its settings.
-
Choose Microsoft Edge as the browser.
-
Save the setting.
-
Check that the run list settings display Microsoft Edge.
-
Start the run list.
-
Review the results for its test cases.
Expected result: Runs started from the run list use its saved browser selection. You can choose Google Chromium instead when you need to run the same list in that browser.
Existing run lists without an explicit browser selection continue to use the applicable default. The settings display the effective browser. Check that displayed value before running an existing list rather than assuming that an earlier Preview choice applies.
Run list browser selection and execution are also supported through Play Chat and MCP. When you change a run list through either route, confirm the saved browser in the run list settings before relying on the next execution.
Use the run list settings to confirm its configuration. A captured application screenshot may not identify the browser used.
Set a team default browser
An authorized user can choose Microsoft Edge or Google Chromium as the default browser in team settings. The team choice applies when a run does not have its own browser selection. An explicit browser selection in run list settings takes precedence over the team default.
The saved team default applies to subsequent runs.
Use the dedicated browser control in team settings. Do not create a browser-default key in the general key/value settings.
Finish the browser session
Disconnect the interactive browser when you have finished. Browser-session credit usage continues while the browser is connected and stops after disconnection. If an inactivity prompt appears, choose whether to remain connected or disconnect.
Check your workspace’s current usage and billing information for the applicable charges.
If Edge does not work as expected
Edge or a region is not available
Check the browser and region options available in your workspace. Ask your workspace administrator to confirm the applicable plan or add-on access. If a region should be available but cannot connect, capture the displayed error and the time of the attempt.
The browser does not launch
Record whether the failure occurred while connecting an interactive session or starting a run list. Include the selected browser, region, test case or run list, and full error text when requesting help. Avoid changing browser-host infrastructure or security settings as a workaround.
The test passes in Chromium but fails in Edge
Identify the first failing step and compare its application state with a successful Chromium run. Include whether the workflow uploads or downloads files, which browser was used to record it, and whether it fails in Preview or a run list. Keep a minimal example that reproduces the difference.
The browser selection is unclear
For Preview, check Browser type before connecting. For a run list, check the browser shown in its saved settings. Do not use an application screenshot alone to identify the browser.