Testcafe execution is stuck while using Chrome Version 130.0.6723.59

shyedhu commented 1 month ago

What is your Scenario?

Looks like Testcafe test execution is stuck while using Chrome Version 130.0.6723.59 with Testcafe Version 3.7.0-rc.1..

I also noticed this issue not happening on same chrome browser version if I was not using following the video option

--video artifacts/videos --video-options singleFile=true,failedOnly=false,pathPattern=${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.mp4

What is the Current behavior?

Chrome browser Version 130.0.6723.59 was opened and test execution is stuck for long hours
Firefox browser was opened and test executed successfully

What is the Expected behavior?

Test should execute successfully

What is the public URL of the test page? (attach your complete example)

none

What is your TestCafe test code?

https://github.com/shyedhu/testcafe-poc/blob/main/README.md

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

git clone https://github.com/shyedhu/testcafe-poc.git
cd testcafe-poc
npm install
npm run test:local:chrome

TestCafe version

3.7.0-rc.1

Node.js version

v22.3.0

Command-line arguments

NONE

Browser name(s) and version(s)

Chrome Version 130.0.6723.59 (Official Build) (x86_64)

Platform(s) and version(s)

MacOS Ventura Version 13.6.6

Other

No response

ayemelyanenko-chegg commented 1 month ago

I am also seeing this issue even without upgrading to TestCafe RC 3.7.0. The tests hang with --disable-native-automation and Chrome 130 and TestCafe version 3.6.2. The issue seems to be with this specific Chrome version 130.0.6723.69-1 which was released today, on October 22nd and that's when the issues started to happen. Seems to also happen on ubuntu/debian images as well

deepanshugoyal1989 commented 1 month ago

I am also getting the same issue,....Testcafe test execution getting stuck while using Chrome Version 130.0.6723.59 with Testcafe Version 3.7.0-rc.1.

github-actions[bot] commented 1 month ago

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.

josephgavin commented 1 month ago

Hey I'm also having the same issue as the others here. Same version of chrome and testcafe. I upgraded testcafe because of the chrome error that was fixed with 3.7.0-rc.1, but now when I run my tests they just hang. This is in headless mode btw, based on context I think others had it not working in headed.

jdnick27 commented 1 month ago

I am also running into this issue. We run through azure pipelines using agents but this is an issue on our local machines as well. We do run headless, but this is also an issue with out headless. We can an error about a websocket.

My testcafe does not "hang" it actually crashes and kills the run.

shyedhu commented 1 month ago

I am also running into this issue. We run through azure pipelines using agents but this is an issue on our local machines as well. We do run headless, but this is also an issue with out headless. We can an error about a websocket.

My testcafe does not "hang" it actually crashes and kills the run.

@jdnick27 you can try testcafe v3.7.0-rc.1 to resolve websocket issue

shyedhu commented 1 month ago

--video

I am also seeing this issue even without upgrading to TestCafe RC 3.7.0. The tests hang with --disable-native-automation and Chrome 130 and TestCafe version 3.6.2. The issue seems to be with this specific Chrome version 130.0.6723.69-1 which was released today, on October 22nd and that's when the issues started to happen. Seems to also happen on ubuntu/debian images as well

I was facing the issue only Chrome version 130 when i was enabled --video options in command line

jdnick27 commented 1 month ago

that worked. Now I am seeing the same issue with the browser opening and what looks to be "hanging". I am seeing a white screen on test start. Is this what you are seeing @shyedhu ?

ayemelyanenko-chegg commented 1 month ago

As a workaround, if you have Microsoft Edge installed, you can use that for your tests for now as Edge is Chromium based

Bayheck commented 1 month ago

Hello,

We have released TestCafe 3.7.0-rc.2, which addresses this issue. Please try it and let us know if the issue is gone.

JavaJung commented 1 month ago

TestCafe 3.7.0-rc.2 looks good so far, on laptop and in ubuntu image run. Just prior to this update it seemed to work to remove screenshot and video options in testcaferc.json as a workaround

Bayheck commented 4 weeks ago

I will close this issue as it was fixed in the PR: https://github.com/DevExpress/testcafe/pull/8315

josephgavin commented 3 weeks ago

After upgrading I am now seeing the following issue instead when I try to run my tests:

ERROR Unable to open the "chrome:headless" browser due to the following error:

Error: connect ECONNREFUSED ::1:53426
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1615:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)

Our tests were functional before the breaking chrome upgrade. As stated above I upgrade to 3.7.0-rc.1 and ran in to the same failure as other above. I have now upgraded to 3.7.0-rc.2

Bayheck commented 3 weeks ago

Please create a separate ticket using this template and also share a Minimal Working Example in that ticket so that the TestCafe team can research the issue and help you.

DevExpress / testcafe