Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testcafe can't work fine with the latest chrome [Version 130.0.6723.70 (Official Build) (64-bit)] #8318

Closed
goodnightql opened this issue Oct 28, 2024 · 3 comments
Labels
STATE: Need clarification An issue lacks information for further research. STATE: Need simple sample A simple sample is required to examine the issue. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@goodnightql
Copy link

What is your Scenario?

Execute test cases using testcafe
testcafe chrome test.js

What is the Current behavior?

The console throws error as fallowing
ERROR Unable to open the "chrome:" browser due to the following error:

Error: WebSocket connection closed
at D:\DDVTest\node_modules\chrome-remote-interface\lib\chrome.js:94:35
at Chrome._handleConnectionClose (D:\DDVTest\node_modules\chrome-remote-interface\lib\chrome.js:256:13)
at WebSocket. (D:\DDVTest\node_modules\chrome-remote-interface\lib\chrome.js:243:22)
at WebSocket.emit (node:events:519:28)
at WebSocket.emit (node:domain:488:12)
at WebSocket.emitClose (D:\DDVTest\node_modules\chrome-remote-interface\node_modules\ws\lib\websocket.js:246:10)
at Receiver.receiverOnFinish (D:\DDVTest\node_modules\chrome-remote-interface\node_modules\ws\lib\websocket.js:1058:20)
at Receiver.emit (node:events:519:28)
at Receiver.emit (node:domain:488:12)
at finish (node:internal/streams/writable:953:10)

What is the Expected behavior?

run testcases fine

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

a private testurl
ip+port+testpage.html

What is your TestCafe test code?

fixture('DDVUITest PerspectiveViewer').page("www.baidu.com").before( ctx=>{
})
.beforeEach(async t=>{

})
.afterEach(t=>{
})
.afterEach(t=>{
})
.after(ctx=>{

}).skipJsErrors();

test("test", t=>{
console.log("test")
})

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

testcafe chrome test.js

TestCafe version

3.1.0

Node.js version

20.17.0

Command-line arguments

testcafe chrome test.js

Browser name(s) and version(s)

chrome Version 130.0.6723.70 (Official Build) (64-bit)

Platform(s) and version(s)

windows 11

Other

No response

@goodnightql goodnightql added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 28, 2024
@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 28, 2024
@Bayheck
Copy link
Collaborator

Bayheck commented Oct 28, 2024

Hello, the issue was fixed at #8300.

We are working on a TestCafe release with the fix right now, but we cannot give you any ETA.

In the meantime, you can try using TestCafe 3.7.0-rc.2 as a temporary solution.

I will be closing this issue as a duplicate.

@Bayheck Bayheck closed this as completed Oct 28, 2024
@testcafe-need-response-bot testcafe-need-response-bot bot removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 28, 2024
@goodnightql
Copy link
Author

goodnightql commented Oct 29, 2024

After I upgraded testcafe to 3.7.0-rc.2, a new problem occurred. I found that I could not draw annotations in live mode, but I could draw them in remote mode. See attachments.

remoteMode-usingChrome.mp4
liveMode-usingChrome.mp4

image
I don't know if it has anything to do with the output in the console.
The same operation worked fine before the browser was upgraded.

@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 29, 2024
@Bayheck Bayheck added STATE: Need simple sample A simple sample is required to examine the issue. and removed STATE: Need response An issue that requires a response or attention from the team. labels Oct 29, 2024
Copy link

Thank you for submitting a bug report. We would love to help you investigate the issue. Please share a simple code example that reliably reproduces the bug. For more information, read the following article: How To Create a Minimal Working Example When You Submit an Issue. We look forward to your response.

@github-actions github-actions bot added the STATE: Need clarification An issue lacks information for further research. label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research. STATE: Need simple sample A simple sample is required to examine the issue. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants