[Feature] Utilize Chrome for Testing

[KotlinIsland]

Chrome has a new distro for automated testing, Playwright should use it instead of Chromium.

https://developer.chrome.com/blog/chrome-for-testing/

[Smrtnyk]

Would be really cool to have versioned chrome binary included in the docker image, like current 3 browsers

[pavelfeldman]

Let's give it few months (a year?) to make sure it passes the test of time. The Chromium land is currently turbulent with a number of new initiatives (New headless, Chrome for Testing) that were not requested by the major testing frameworks. It is a little tricky to navigate those waters right now and the best strategy is to wait and see:

• why and how different the new ports will be,
• whether they will be covered with the tests upstream and
• whether they will be maintained and shipped along with the existing channels.

If you have a bug report and/or a feature request that shows how Chrome for Testing is better, please describe your scenario in a separate issue.

[edelreal]

I like the Chrome-for-Testing approach approach Puppeteer is taking to reduce feature gaps between Chrome and Chromium. Hoping the Chrome-for-Testing works out well and can be integrated into Playwright.

[DetachHead]

this issue should be re-opened imo. there are features such as the self XSS warning that are annoying when debugging tests in chromium, which chrome for testing fixes: #30425 (comment)