How To Disable Chrome Auto-Update for Test Environments

How To Disable Chrome Auto-Update for Test Environments

Problem

Google Chrome will auto-update when a new version becomes available.  When this occurs, the Chrome Webdriver being used by Cycle will no longer match the version of Chrome and may become unstable.

Solution

To prevent unexpected issues, Chrome auto-updates should be disabled in test environments.  

Step 1: Disable Google Update service

Open the Windows System Configuration application (msconfig.exe).

Within the Services tab, find and uncheck Google Update Service (gupdatem), then select Apply.

mceclip0.png

Step 2: Disable Scheduled Google Updates

Open Task Scheduler, under Active Tasks, double click the task GoogleUpdateTaskMachineUA

On this page, disable both GoogleUpdateTaskMachineCore and GoogleUpdateTaskMachineUA.

 mceclip1.png

Note: Keeping Chrome up to date can be important for system security.  Once the newest release of Chrome has been confirmed to be stable with Cycle, Chrome, and the ChromeDriver for Cycle should be updated.

Instructions on updating ChromeDriver can be found here:

Update your ChromeDriver

    • Related Articles

    • How to use Web API steps

      Web API steps introduced in Cycle 2.5 can be used to send HTTP requests to exposed web API endpoints. The Cycle Web API steps support POST and GET request methods using the JSON data format. Cycle also includes steps for handling HTTP responses ...
    • How to make better xpaths for web tests.

      Problem My web-based steps in Cycle are not finding the elements I want them to, or finding the wrong elements and giving me false-positives. Solution When possible, it is best to define elements to interact with on a web page by a static value that ...
    • My web-based Cycle tests are failing.

      Problem My browser-based Cycle Features are failing. Solution Check that the following common mistakes are not causing your failures: 1. Opening the browser first Any browser-based Steps in Cycle should be preceded in their Scenario with: I open ...
    • How to load and clean up test data efficiently in Cycle.

      Problem In order to properly evaluate system behavior it is required that known inputs produce desired outputs. This is especially critical when working with the JDA WMS due to its multitude of configuration options that drive specific system ...
    • Does Cycle have a way to test the Integration Layer of my WMS?

      Problem System communications while critical can be overlooked in the testing Cycle. Especially when the integration layer is run by different groups within an organization, trying to get valid data coordinated is often difficult. Solution Cycle ...