Skip to content

Commit 737f963

Browse files
committed
docs: add Chrome for Testing to main README
1 parent b538094 commit 737f963

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,10 @@ Cypress officially [supports][Cypress Browser Support] the latest 3 major versio
5252
[Chromium]: https://www.chromium.org/Home/
5353
[Cypress Browser Support]: https://docs.cypress.io/app/references/launching-browsers#Browser-versions-supported
5454

55+
### Chrome for Testing
56+
57+
[Google Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) is an alternate version of Chrome which is supported by [Cypress 13.17.0](https://docs.cypress.io/app/references/changelog#13-17-0) and above. The [examples/chrome-for-testing](./examples/chrome-for-testing/) directory shows how it can be built into a custom Cypress Docker image.
58+
5559
### Mozilla geckodriver
5660

5761
[cypress/browsers](./browsers/) and [cypress/included](./included/) images with Firefox `139.0.1` and above are built with the [Mozilla geckodriver](https://github.com/mozilla/geckodriver) included. This driver is needed to test when using Firefox with Cypress versions >= [13.15.1](https://docs.cypress.io/app/references/changelog#13-15-1). The environment variable `GECKODRIVER_PATH` points to the driver located at `/opt/geckodriver/geckodriver`. Earlier images, that do not include the driver, may attempt to download the driver at run-time when testing Firefox, causing failures in air-gapped network environments with no Internet access.

0 commit comments

Comments
 (0)