Testcafe stopped running with latest chrome update
jwhitmore-fleetresponse opened this issue · 6 comments
What is your Scenario?
Running test suite pointed to chrome browser after upgrading to Version 130.0.6723.70 (Official Build) (64-bit)
What is the Current behavior?
An error is displayed in the console
Error: WebSocket connection closed
at C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\chrome-remote-interface\lib\chrome.js:94:35
at Chrome._handleConnectionClose (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\chrome-remote-interface\lib\chrome.js:256:13)
at WebSocket. (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\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 (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\ws\lib\websocket.js:246:10)
at Receiver.receiverOnFinish (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\ws\lib\websocket.js:1060: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?
Tests should run as before
What is the public URL of the test page? (attach your complete example)
There is no public URL, I just have all my tests suites as before and when I execute I get the following error above
What is your TestCafe test code?
Never gets to test code errors out running cli
testcafe ./tests/**
Your complete configuration file
{
"browsers": "chrome",
"concurrency": 1,
"hostname": "localhost",
"reporter": [
{
"name": "spec"
},
{
"name": "xunit",
"output": "e2eReport.xml"
}
],
"selectorTimeout": 20000,
"assertionTimeout": 20000,
"pageLoadTimeout": 120000,
"pageRequestTimeout": 120000,
"speed": 0.8,
"screenshots": {
"takeOnFails": true,
"pathPattern": "${BROWSER}/${FIXTURE}/${TEST}.png"
}
}
Your complete test report
ERROR Unable to open the "chrome:" browser due to the following error:
Error: WebSocket connection closed
at C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\chrome-remote-interface\lib\chrome.js:94:35
at Chrome._handleConnectionClose (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\chrome-remote-interface\lib\chrome.js:256:13)
at WebSocket. (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\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 (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\ws\lib\websocket.js:246:10)
at Receiver.receiverOnFinish (C:\Users\jwhitmore\AppData\Roaming\npm\node_modules\testcafe\node_modules\ws\lib\websocket.js:1060:20)
at Receiver.emit (node:events:519:28)
at Receiver.emit (node:domain:488:12)
at finish (node:internal/streams/writable:953:10)
Screenshots
No response
Steps to Reproduce
- Execute cli with chrome set as the browser
TestCafe version
3.6.2
Node.js version
20.16.0
Command-line arguments
testcafe ./tests/**
Browser name(s) and version(s)
Chrome Version 130.0.6723.70 (Official Build) (64-bit)
Platform(s) and version(s)
Windows 11 Enterprise v 10.0.26100 buiild 26100
Other
Worked fine the version before updating..129
I've encountered a similar issue.
@jwhitmore-fleetresponse you can try testcafe v3.7.0-rc.1 to resolve websocket issue
@jwhitmore-fleetresponse you can try testcafe v3.7.0-rc.1 to resolve websocket issue
I have the same issue.
Unfortunately it didn't help.
As a workaround, if you have Microsoft Edge installed, you can use that for your tests as Edge is Chromium based