These can be used instead of the latest-versions-per-milestone, latest-patch-versions-per-build, and last-known-good-versionsJSON API endpoints respectively.
How to install the system-level dependencies required for archived linux64 binaries?
unzip chrome-linux64.zip;
apt-get update;
while read pkg; do
apt-get satisfy -y --no-install-recommends "${pkg}";
done < chrome-linux64/deb.deps;
macOS says the *.app is damaged. What now?
On macOS, if you download a Chrome for Testing ZIP file using a browser instead of via @puppeteer/browsers, curl, or wget, you might get this warning:
“Google Chrome for Testing.app” is damaged and can’t be opened. You should move it to the Trash.
This happens because macOS Gatekeeper 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:
xattr -cr 'Google Chrome for Testing.app'
Support
For bug reports with the CfT dashboard and/or API (i.e. the code in this repository): file an issue
Chrome for Testing availability
JSON API endpoints
known-good-versions.jsonknown-good-versions-with-downloads.jsondownloadsproperty for each version, listing the full download URLs per asset.last-known-good-versions.jsonlast-known-good-versions-with-downloads.jsondownloadsproperty for each channel, listing the full download URLs per asset.latest-patch-versions-per-build.jsonMAJOR.MINOR.BUILDversions.latest-patch-versions-per-build-with-downloads.jsondownloadsproperty for each version, listing the full download URLs per asset.latest-versions-per-milestone.jsonlatest-versions-per-milestone-with-downloads.jsondownloadsproperty 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.
Supported binaries
The current list of supported binaries is:
chromea.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)Supported platforms
The current list of supported platforms is:
linux64mac-arm64mac-x64win32win64Other API endpoints
For historical reasons,
LATEST_RELEASE_files containing fully qualified version numbers are available as well.https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116answers the question “what’s the latest available version within milestone 116?”.https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116.0.5845answers the question “what’s the latest available version within the 116.0.5845.* range?”.https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_STABLEanswers 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, andlast-known-good-versionsJSON API endpoints respectively.Additionally, each version from the
known-good-versions-with-downloads.jsonis 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.
CLI utilities
Find the latest Chrome versions across channels
Check a specific Chrome version for CfT binary availability
FAQ
What is Chrome for Testing?
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.
What’s the easiest way to download Chrome for Testing binaries?
Use
@puppeteer/browsers.How to install the system-level dependencies required for archived
linux64binaries?macOS says the
*.appis damaged. What now?On macOS, if you download a Chrome for Testing ZIP file using a browser instead of via
@puppeteer/browsers,curl, orwget, you might get this warning:This happens because macOS Gatekeeper 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:
Support
chrome-for-testingtag