When developing web applications or running automated tests, have you ever encountered issues like your Chrome browser suddenly updating, causing previously working scripts to break? Or perhaps while debugging, you're unsure if a bug is caused by your code or a browser version update?
To address these concerns, Google has introduced a special version – Chrome for Testing. This isn't a traditional beta (Beta/Dev/Canary) release, but rather an independent "flavor" specifically designed for developers and automated testing.
The most significant feature of Chrome for Testing is that it does not update automatically. In fact, it cannot be updated manually.
Unlike the Chrome you use daily, Chrome for Testing isn't installed via an installer. You download a ZIP archive containing all the browser files, and then you simply run the executable file after extracting it. Each specific version and release channel (Stable/Beta/Dev/Canary) has its own independent download package.
This design means you, as a developer, have complete control over which Chrome version you use, without the worry of it unexpectedly updating at a critical moment.
Consider these scenarios:
• Debugging Extensions or Scripts: You're troubleshooting a complex bug, and suddenly Chrome updates in the background. The bug's behavior changes, and you can't determine if it's your code or the browser update causing the issue, making debugging much harder.
• Version Compatibility Testing: Your web application stops working after a Chrome update. With Chrome for Testing, you can download older versions for comparative testing, pinpointing precisely which Chrome version introduced the problem.
• Automated Testing Scenarios: You have a suite of automated tests running in your CI/CD pipeline. If Chrome updates automatically, it could lead to unexpected test failures, disrupting your deployment process. Chrome for Testing ensures a consistent testing environment.
There's no prominent "Download" button for Chrome for Testing because its core design is for developers to select specific versions.
Google provides API endpoints and related tools to acquire specific versions:
• Dashboard Page: Lists the latest versions for each release channel.
• GitHub Repository: Offers a comprehensive list of versions and JSON-formatted API endpoints.
• API Requests: Automate the download of specific versions via scripts.
Typically, developers write scripts to automatically fetch the required versions. On the GitHub "Known Good Versions" API list, you can find all versions from May 2023 (version 113, when Chrome for Testing was first released) to the present, including all patch versions under each major version number.
While Chrome for Testing strives to be consistent with regular versions, there are a few notable distinctions:
• Top Banner: A banner is always displayed at the top of the browser window, reminding you: "Chrome for testing is only for automated testing. For regular browsing, use a standard version of Chrome that updates automatically." This is to prevent users from using it as their daily browser.
• Name Identification: In menus like Settings, it will display "Chrome For Testing" instead of simply "Chrome."
• Branding Details: Some interface elements might show "Chromium" instead of "Chrome," such as in the profile login section.
Chrome for Testing may have certain experimental feature flags enabled or disabled by default. For example, some users have noted that Chrome for Testing of the same version number enables the new extension management menu by default, whereas in the regular version, this requires manual activation via flags.
It's important to note that these differences primarily concern default configurations rather than the core functionality itself. The underlying philosophy of Chrome for Testing is to be as close as possible to the corresponding version of regular Chrome, with potential variations only in the default state of certain experimental features.
On Windows systems, Chrome for Testing uses a separate user data directory (located in the AppData folder). This means it won't share bookmarks, extensions, cookies, or other data with other Chrome versions you might have installed.
Chrome for Testing is not designed for general users. Its typical use cases include:
• Development Environment Isolation: Use a specific version during local development to prevent browser updates from impacting your progress.
• Automated Testing Frameworks: Integrate with tools like Selenium and Puppeteer to ensure fixed versions in your testing environment.
• Version Compatibility Verification: Quickly switch between different versions for compatibility testing.
• Bug Reproduction and Debugging: Lock down a specific version to accurately reproduce and investigate issues.
Although Chrome for Testing is fully functional, Google explicitly advises against using it as your primary daily browser. The reason is simple: the lack of automatic updates means no security patches, posing a security risk with prolonged use.
Chrome for Testing is functionally very similar to the regular version of Chrome for the same version number. The main differences are the absence of automatic updates and potentially different default configurations for certain experimental features. Its design goal is to be as close as possible to the regular version, ensuring the accuracy of test results.
This is not recommended. Chrome for Testing does not update automatically, meaning it won't receive timely security patches and bug fixes, posing a security risk with long-term use. Google also explicitly indicates in the interface that this version is solely for automated testing.
Visit the Chrome for Testing GitHub page. You can find all available versions in the "Known Good Versions" API endpoint. You can either make API requests or download the ZIP file for your desired version directly from the Dashboard.
Chrome for Testing offers downloadable versions for Windows, macOS, and Linux. Each platform has build versions available for different release channels (Stable/Beta/Dev/Canary).
Yes. Because Chrome for Testing uses an independent user data directory and doesn't require installation, you can run multiple different versions of Chrome for Testing concurrently. They will not interfere with each other or with any regular Chrome versions you have installed.
Outline
.png)
