Unable to update chrome drivers/tests running too fast after latest updating Chrome Version 137.0.7151.41

Feedback & Reviews Bugs Report
1

Hello everyone,

After my chrome updated to Version 137.0.7151.41 I am unable to update my chrome drivers.
See snapshot.

The majority of my tests are failing because they are executing too fast.
I did some research and this happens due to the updated browser version and its impact on the Webdriver compatibility. I tried manually replacing the Webdriver to the latest version that matches my chrome version here: Chrome for Testing availability
which is 137.0.7151.40 but my chrome browser is at 137.0.7151.41 so there is a mismatch.

Anyone have a solution for this?

Thanks so much.

Screenshot_052525_081416_AM
Screenshot_052525_081416_AM2479×1679 205 KB

3 Likes
3

Hi @devon,

Thank you for letting us know. I will create the ticket for this to let my team investigate. Can you please help give more information such as KS version, OS, browser version, error log, step by step reproduce, …? Thank you

4

does your test case fail even after replacing the drivers manually?

5

Katalon posted a workaround:

6

I have the same problem

7

Yes they still fail.

8

If you only use the Web Recorder for creating your test scripts, then you are likely going to have your test fail over time. When you use the Web Recorder, your scripts do not take into account the amount of time behind-the-scenes that your network takes to refresh your browser. You should go in after recording, and add ‘waitFor*’ statements to allow your script to adjust to the speed of your browser. So, it is likely your tests are failing because you are not letting your script pause in the right places.

As an example, when starting the browser (I might go a bit overboard on my delays, but the tests complete nicely):

WebUI.navigateToUrl(gSiteUrl)
WebUI.waitForPageLoad(10)

WebUI.waitForElementVisible(findTestObject('myPage/input_UserName'), 10)
WebUI.verifyElementVisible(findTestObject('myPage/input_UserName'))
WebUI.setText(findTestObject('myPage/input_UserName'), 'gUserName')
...

And after any page change:

WebUI.verifyElementClickable(findTestObject('myPage/a_DocReview'))
WebUI.click(findTestObject('myPage/a_DocReview'))
WebUI.waitForPageLoad(10)

WebUI.waitForElementVisible(findTestObject('myPage/Sheet/input_Message'), 10)
WebUI.verifyElementVisible(findTestObject('myPage/Sheet/input_Message'))
1 Like
9

Katalon posted this: https://katalon-inc.my.site.com/support/article/Recorder-Fails-to-Launch-on-Chrome-137 . In this post, Katalon suggested a way to use Chrome for Testing. Katalon wrote

“Until an official fix is released, use Chrome for Testing as a temporary solution”.

No. I have an opposite idea. In order to run tests stably in Katalon Studio, “Chrome for Testing” is better than the ordinary Chrome browser.

Why? — You can fix the version of “Chrome for Testing”, whereas the ordinary Chrome browser automatically/silently updates its version. Auto-updates is likely to introduce unexpected internal change in Chrome , that could cause sudden problems as this issue.

Auto-updates: it’s greate for users, painful for developers.

So you should prefer “Chrome for Testing”.

I believe that all Katalon Studio users want to test their own web app; they don’t want to test the Chrome browser itself. So we should fix the browser version.

1 Like
10

Hi all,

Thank you all for raising this concern. We have acknowledged this and plan to fix it soon. While the fix is still planning, we would love to suggest the workaround here and I will update this back with anything new. Thank you

11

Katalon posted this: https://katalon-inc.my.site.com/support/article/Recorder-Fails-to-Launch-on-Chrome-137 . In this post, Katalon suggested to use Chrome for Testing. Unfortunately, this explanation is NOT useful to get the older version 136 of Chrome for Testing. The article write:

  1. Download Chrome for Testing: Chrome for Testing availability

If you visit this URL today, the page will show you the links to the version 137.x and newer of Chrome for Testing. the page does not give you the links to the older version 136.x, which we need now to workaround the problem.

Let me tell you alternative way to get the version 136.x of Chrome for Testing. Please refer to my previous post:

You should use npx @puppeteer/browsers install command, that is the official method which the Chrome development team supports.

Here I assume you have “Node” and “npx” installed on your machine (I suppose that all of serious Web developers would have installed Node already).

To install Chrome for Testing v136, in the terminal window, you want to run

$ npx @puppeteer/browsers install chrome@136

When finished, the command will display the exact path of the “Chrome for Testing” binary. You want to memorize the path and use it in Katalon.

To install ChromeDriver v136, in the terminal window, you want to run

$ npx @puppeteer/browsers install chromedriver@136
12

@gabriela.pinto reported that once he/she had a problem with Chrome 137.0.7151.55; switched to Chrome for Testing v137.0.7151.55; then his/her problem was fixed.

This report makes me puzzled. This report indicates that Chrome browser 137.0.7151.55 and Chrome for Testing 137.0.7151.55 behaves differently.

This is a surprise for me. The Chrome team wrote Chrome for Testing: reliable downloads for browser automation  |  Blog  |  Chrome for Developers where they promised that Chrome browser and Chrom for Testing work no differently except auto-updates.

… Chrome is a software too much sophisticated for me. I cannot really understand it.

13

Hi all,

We have just released 10.2.1 which contains a hotfix for this issue. Can you please help to check the issue with the latest version? Let me know if it works/not work. Thank you