[Req-81] Playwright-Selenium Dual-Driver Implementation

[nasif-z]

Runtime Parameter: BROWSER_DRIVER

• This runtime parameter can be set to the value of either playwright or selenium
• Ensures all web actions in the test case will be executed through the chosen driver in this parameter, regardless of what was chosen in the steps
• Example: test case contains steps all of which use selenium action - BROWSER_DRIVER is set to playwright - all those actions will be converted to playwright action internally by Node at runtime

Optional Parameter: browser driver

This works similarly to the runtime parameter above but this takes the highest priority when both parameters are in place. This is meant to override the driver preference only for certain actions, allowing the user to have fine-grained driver selection for their steps even when using the runtime parameter to set a global driver preference.

• browser driver | optional parameter | playwright or selenium
• The above row can be added to any web action and it will convert it to an action of the driver in the parameter
• Example: if the action is selenium action - and if this optional parameter is set to playwright - the action will be converted to playwright action internally by Node

Seamless driver switching

• Any browser launched with Selenium will be automatically connected to a Playwright instance in the background
• Any browser launched with Playwright will be automatically connected to a Selenium instance in the background
• This allows playwright action to run on Selenium-launched browsers and selenium action to run on Playwright-launched browsers
• Only works on Chromium-based browsers since it uses Chrome DevTools Protocol (CDP) to establish a remote debugging bridge connection
• Simplified diagram on how this works:

[sazid]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7bf65e1a4d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Normalize routed driver name before building action subfield

The routing check accepts BROWSER_DRIVER case-insensitively, but this assignment uses the raw runtime value, so inputs like Playwright or selenium become Playwright action / selenium action and then fail module resolution in get_module_and_function (which matches module tokens exactly). This makes the new runtime override intermittently break based on capitalization/spacing even though the validation path explicitly treats those values as valid.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Populate Playwright globals when attaching to Selenium session

This bridge only sets PlaywrightBuiltInFunctions.current_page, but does not set Playwright's context/browser globals, so actions that depend on context (for example tab/window operations that explicitly fail when context is None) still break after a Selenium-launched attach. That means the new “seamless switching” path is incomplete for a non-trivial subset of Playwright actions.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Avoid hard-coding a single CDP port for all browser launches

Using a fixed --remote-debugging-port=9222 for every Playwright launch causes deterministic port collisions when more than one browser instance is opened (for example multiple page_id sessions) or when runs overlap on the same machine, leading to failed launches or attaching to the wrong target. The same constant is also used by the attach path, so this becomes a systemic single-port bottleneck rather than a per-session bridge.

Useful? React with 👍 / 👎.