Chrome for Testing availability JSON API endpoints | Endpoint | Description | | -----------------------------------------------------------…
Chrome for Testing availability JSON API endpoints | Endpoint | Description | | -----------------------------------------------------------…
| Endpoint | Description |
|---|---|
known-good-versions.json |
The versions for which all CfT assets are available for download. Useful for bisecting. |
known-good-versions-with-downloads.json |
Same as above, but with an extra downloads property for each version, listing the full download URLs per asset. |
last-known-good-versions.json |
The latest versions for which all CfT assets are available for download, for each Chrome release channel (Stable/Beta/Dev/Canary). |
last-known-good-versions-with-downloads.json |
Same as above, but with an extra downloads property for each channel, listing the full download URLs per asset. |
latest-patch-versions-per-build.json |
The latest versions for which all CfT assets are available for download, for each known combination of MAJOR.MINOR.BUILD versions. |
latest-patch-versions-per-build-with-downloads.json |
Same as above, but with an extra downloads property for each version, listing the full download URLs per asset. |
latest-versions-per-milestone.json |
The latest versions for which all CfT assets are available for download, for each Chrome milestone. |
latest-versions-per-milestone-with-downloads.json |
Same as above, but with an extra downloads property for each milestone, listing the full download URLs per asset. |
The set of “all CfT assets” for a given Chrome version is a matrix of supported binaries × platforms.
The current list of supported binaries is:
chrome a.k.a. Chrome for Testing (supported since v113.0.5672.0)chromedriver (supported since v115.0.5763.0)chrome-headless-shell (supported since v120.0.6098.0)The current list of supported platforms is:
linux-arm64 (supported since v153.0.8001.0)linux64mac-arm64mac-x64win32win64For historical reasons, LATEST_RELEASE_ files containing fully qualified version numbers are available as well.
https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116 answers the question “what’s the latest available version within milestone 116?”.https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116.0.5845 answers the question “what’s the latest available version within the 116.0.5845.* range?”.https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_STABLE answers the question “what’s the latest available Stable channel version?”. Similar for the other channels (BETA/DEV/CANARY).These can be used instead of the latest-versions-per-milestone, latest-patch-versions-per-build, and last-known-good-versions JSON API endpoints respectively.
Additionally, each version from the known-good-versions-with-downloads.json is published as a separate JSON file containing its download URLs — for example, 123.0.6309.0.json.
You can browse the complete list of JSON and text files.
……Chrome for Testing is a new Chrome flavor that specifically targets web app testing and automation use cases. Read Chrome for Testing: reliable downloads for browser automation for more details.
Use @puppeteer/browsers.
linux64 binaries?unzip chrome-linux64.zip;
apt-get update;
while read pkg; do
apt-get satisfy -y --no-install-recommends "${pkg}";
done “Google Chrome for Testing.app” is damaged and can’t be opened. You should move it to the Trash.
This happens because macOS [Gatekeeper](https://support.apple.com/guide/security/gatekeeper-and-runtime-protection-sec5599b66df/web) sets an extended attribute that marks the ZIP file and any files within it as “downloaded via a browser” and thus potentially dangerous.
To fix the problem, recursively remove the extended attribute:
```sh
xattr -cr 'Google Chrome for Testing.app'chrome-for-testing tagNo open issues yet, or sync has not completed.