Testcafe can't work fine with the latest chrome [Version 130.0.6723.70 (Official Build) (64-bit)] #8318
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).
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
The text was updated successfully, but these errors were encountered: