You have the ability to specify the versions of Chrome that are run on any node when "Stable" or "Preview" are selected. When you choose a specific version, it works the same as before: if that version is present, it runs. Otherwise it runs on the version that is less than or equal to the 'Stable' version configured for that system.
The Stable and Preview versions are per-system. When we deploy, we test on backbone nodes because we have control over that environment. Due to different customers' Enterprise node configurations, we are unable to test that a new version of Chrome will fully work. Because there is a single version dropdown, and tests can be configured which target nodes with different Stable and Preview versions, the dropdown shows the versions that are configured to run on Backbone nodes. The actual Stable and Preview versions for targeted Enterprise nodes may differ.
If you wish to set an Enterprise node to run a different Stable/Preview version of Chrome than it is currently using, you can work with Support to:
- Verify that the version they would like set as 'Stable' works properly on their node by running a 'specific version' test for that version. If there are issues running such a test, Support can help reconfigure the node to work with the new version of Chrome. - Once Support has verified that the new version of Chrome works on the customer's Enterprise node(s), we will open an escalation ticket for a DB change, which includes the Node and Machine IDs, as well as the versions of Chrome which the customer would like as Stable and Preview.
Once the database change is completed, tests configured with 'Stable' or 'Preview' will start using the new version.
When you are ready to start the process, please open a support ticket at https://support.catchpoint.com/hc/en-us/requests/new or by sending an email to support@catchpoint.com.