The Chrome version has changed for all webdriver scripts after the DX ASM maintenance

Products

• CA App Synthetic Monitor

Issue/Introduction

We noticed that after the ASM maintenance all our webdriver monitors have been reconfigured with a different "Chrome ###" as the browser, however we had initially configured them with "Chrome" without any version.

Environment

• DX ASM

Resolution

The update policy is as follows:

We always keep the last 3 versions of both browsers (Chrome and Firefox), let's say we have A, B and C, the C being the latest one. When we deploy a new version, D, the latest version (A) is removed from public stations. If customers' monitors were running on the latest version before the release, it was the version C. After the release, we fix all monitors using the latest version to version C. This way, we know that the monitors won't start failing after the release, triggering alerts and causing troubles, furthermore by night. Customers can, when the time is suitable to them, login to ASM, select all monitors using the old browser (search for "browser:old", see the attached screenshot) and select "Switch to the latest browser" in one step:

 

 

 

In case something goes wrong customer can switch the failing monitors back to the previous version and fix the issue.

Additional Information

Techdocs - Using ASM