test: add Chrome for Testing example

[MikeMcC399]

Issue

Google Chrome for Testing is not part of the factory build process and it is not yet documented how to include it in a custom-built Cypress Docker image. Cypress 13.17.0, released Dec 17, 2024, and above, support this browser.

The Google Chrome browser (not Google Chrome for Testing) is currently packaged into Cypress Docker Linux/amd64 images in the repositories cypress/browsers and cypress/included.

Note that neither "Chrome" nor "Chrome for Testing" are currently available for the Linux/arm64 platform.

Benefits

Adding an example for Chrome for Testing, benefits Cypress Docker users who want to test against Chrome for Testing inside Docker. The Blog announcement for Chrome for Testing cites the lack of auto update and ability to install a specific version as the main advantages of Chrome for Testing.

@puppeteer/browsers, with its download option for Chrome for Testing, conveniently allows version selection:

• by explicit full version e.g. 131.0.6778.204
• by major version e.g. 131
• by channel alias:
  • stable
  • beta
  • dev
  • canary

The flexible version selection is an advantage compared to the Cypress Docker factory process which allows only a full version specification to select a Chrome version. No selection using major version or channel alias is allowed in the Cypress Docker factory process.

Change

• Add a sub-directory chrome-for-testing to the examples directory.
• Provide a working example of installing the Chrome for Testing browser in a Cypress Docker image and running it with Cypress.

References

Google Chrome for Testing:

• Blog
• List of current versions
• Repository
• Available downloads

Installation using

• @puppeteer/browsers

Verification

Ubuntu 24.04.1 LTS, Node.js 22.12.0 LTS, Docker Desktop 4.37.1

git clone https://github.com/cypress-io/cypress-docker-images
cd cypress-docker-images
cd examples/chrome-for-testing
./scripts/test.sh

Also verified in actions/workflows/example-tests.yml.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[jennifer-shehane]

@jennifer-shehane Is there a reason this is in draft?

[MikeMcC399]

CI has failed due to transient network errors, such as the inability to reach https://on.cypress.io/wait