vasilyevi
commented
1 month ago nothing works at all to me
Closed AlekseyKravtsov17 closed 1 month ago
vasilyevi
commented
1 month ago nothing works at all to me
AlekseyKravtsov17
commented
1 month ago After updating to chrome 130 all new executions fails with the same error:
The "concurrency" and "quarantineMode" options from the configuration file will be ignored. ERROR Unable to open the "chrome:headless" browser due to the following error:
Error: WebSocket connection closed
at tests\node_modules\chrome-remote-interface\lib\chrome.js:94:35
at Chrome._handleConnectionClose (tests\node_modules\chrome-remote-interface\lib\chrome.js:256:13)
at WebSocket.
RafaelBeltranClip
commented
1 month ago @AlekseyKravtsov17, I've been following issue #8300, and there is a fix for it in the latest release candidate (3.7.0). However, after testing it, I encountered a new issue: I am unable to log in, as I can't interact with the page elements. The elements are detected, but I'm unable to write into or click on them. Could you please take a look?
gforepsly
commented
1 month ago I see some thumbs up for this issue under the first topic meant for this bug: https://github.com/DevExpress/testcafe/issues/8240
I will link it for the reference - We have the same issue, so I'm using Edge for now as a workaround. But this is very nasty and a complete blockage for us.
Bayheck
commented
1 month ago Hello @AlekseyKravtsov17,
We have released testcafe 3.7.0-rc.1, which addresses this issue.
Please take a look and let us know your results.
I will close this issue as a duplicate of https://github.com/DevExpress/testcafe/issues/8300.
vasilyevi
commented
1 month ago 3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
AlekseyKravtsov17
commented
1 month ago 3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me
gforepsly
commented
1 month ago 3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me.
3.7.0-rc.1 does not work for me at all, it jsut failed on github actions timeout. Seems tests are just stuck
Same for me
Same for me.
Explanation: https://github.com/DevExpress/testcafe/issues/8307
@Bayheck I've noticed the spec reporter hangs when it needs to throw an error. It's quite easily reproduced on v3.7.0-rc.1
Bayheck
commented
1 month ago Hello @AlekseyKravtsov17,
I believe you have encountered this issue: https://github.com/DevExpress/testcafe/issues/8300.
Please stay tuned - we are already working on it.
What is your Scenario?
We have a set of tests which executes every 30 mins 24/7
What is the Current behavior?
We have around 50 executions per day, but starting from yesterday, about 20-30% of these executions started failing with the following error: The "concurrency" option from the configuration file will be ignored. ERROR Unable to open the "chrome:headless" browser due to the following error:
Error: WebSocket connection closed at /home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:94:35 at Chrome._handleConnectionClose (/home/runner/work/tests/node_modules/chrome-remote-interface/lib/chrome.js:256:13) at WebSocket. (/home/runner/work/tests/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 (/home/runner/work/tests/node_modules/ws/lib/websocket.js:246:10)
at Socket.socketOnClose (/home/runner/work/tests/node_modules/ws/lib/websocket.js:1148:15)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at TCP. (node:net:339:12)
Type "testcafe -h" for help.
We already tried to change browsers value to the following, but it didn't change anything:
browsers: "chrome:headless --disable-search-engine-choice-screen",Here is the testcafe debug log for such failure:
What is the Expected behavior?
Should work as well as other successful executions
What is the public URL of the test page? (attach your complete example)
N/A
What is your TestCafe test code?
N/A
Your complete configuration file
module.exports = { screenshots: { path: "./artifacts/screenshots", takeOnFails: false, pathPattern: "${DATE}${TIME}/${TEST}/${FILE_INDEX}${QUARANTINE_ATTEMPT}.png", thumbnails: false }, disableMultipleWindows: true, browsers: "chrome:headless --disable-search-engine-choice-screen", concurrency: 2, skipJsErrors: true, browserInitTimeout: 120000, pageLoadTimeout: 60000, pageRequestTimeout: 65000, selectorTimeout: 20000, testExecutionTimeout: 900000, quarantineMode: false, disableNativeAutomation: false, testResults, }
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
N/A
TestCafe version
3.6.0
Node.js version
Tried with both v18 and v20
Command-line arguments
yarn testcafe
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response