fix: add chrome for testing dependencies to example

[MikeMcC399]

Situation

In the examples/chrome-for-testing > README Google Chrome for Testing is installed using @puppeteer/browsers

The instructions to install system dependencies using the following from the README for @puppeteer/browsers was not used, because it did not work:

npx puppeteer browsers install chrome --install-deps

Although the example runs without checking for all dependencies, there may be some edge cases that need the complete set of dependencies installed.

Change

In examples/chrome-for-testing/Dockerfile use installed contents of /opt/chrome-for-testing/deb.deps to install any missing dependencies.

Verification

Execute the following:

cd examples/chrome-for-testing              # Use a pre-configured simple Cypress E2E project
npm ci                                      # Install all dependencies
docker build --progress plain -t test-chrome-for-testing .   # Build a new image
docker run --rm --entrypoint bash test-chrome-for-testing -c "npx cypress run --browser chrome-for-testing" # Run Cypress test using Chrome for Testing

[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.

[MikeMcC399]

• Due to a current npm outage https://status.npmjs.org/incidents/dn5mcp85737y this PR failed CI tests on merge into the master branch. According to npm, a fix is in progress

[AtofStryker]

• Due to a current npm outage https://status.npmjs.org/incidents/dn5mcp85737y this PR failed CI tests on merge into the master branch. According to npm, a fix is in progress

@MikeMcC399 once the outage is over Ill re kick off this job

[MikeMcC399]

@AtofStryker

once the outage is over Ill re kick off this job

Thank you very much for your offer! This would make sense, as otherwise the README will continue to show a failed build.

https://status.npmjs.org/incidents/dn5mcp85737y is marked

Resolved
This incident has been resolved.
Posted 17 hours ago. Jun 12, 2025 - 20:58 UTC

[AtofStryker]

@AtofStryker

once the outage is over Ill re kick off this job

Thank you very much for your offer! This would make sense, as otherwise the README will continue to show a failed build.

https://status.npmjs.org/incidents/dn5mcp85737y is marked

Resolved This incident has been resolved. Posted 17 hours ago. Jun 12, 2025 - 20:58 UTC

@MikeMcC399 images should now be published!

[MikeMcC399]

@AtofStryker

images should now be published!

Thanks for following up! In fact there were no images to publish, only examples, and the GitHub Actions job also failed due to the npm HTTP 504 issue, so theoretically, this would also need to be re-run.

However, in the meantime, I realised that I made a mistake in this PR and I forgot to update the Chrome for Testing example README. I guess I was jumping between too many repos and related issues in parallel and I got this wrong.

So, no need to re-run here. I've submitted a new PR #1370 to fix the README, and if that merges correctly, then we'll be fine!