Open cwalker-reveille opened 1 year ago
I wanted to second this. I believe just allowing codegen to utilize the launch_persistent_context() function on the browsers that are specified would work, so that an executable_path can be set.
We recommend the 'Record using custom Setup' for that:
const { chromium } = require('@playwright/test');
(async () => {
const browser = await chromium.launch({ headless: false, channel: 'chrome' });
const context = await browser.newContext();
const page = await context.newPage();
await page.pause();
})();
Calling page.pause()
will open Codegen: https://playwright.dev/docs/api/class-page#page-pause
We run our tests on a machine using its OS based Chrome instead of chromium
I know that the current options for codegen -b are 'chromium','firefox' and 'webkit'. We would like to add 'chrome' to the list. In many of our cases, testscripts are generated not by a developer but an enduser who probably does not have a version of chromium installed. They would also question why their 'Chrome' icon while in codegen is blue rather than the 'normal' red,green,yellow icon.