Closed RafaelBeltranClip closed 4 weeks ago
I am facing the same problem when running my tests locally. Nothing happens when clicking on checkboxes, buttons, etc.
Same issue here. As soon as our build agents got a new image containing Chrome 130, all tests starting to fail.
Note that the problem does not seem to affect Edge 130 (which is also Chromium-based).
Same issue with Chrome 130, we move to Edge as workaround, but our application is built for Chrome
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.
The new release you have pushed out is that for TestCafe Studio or open source? Where can I download new version of the Testcafe Studio? Thanks. The website is still pointing to Testcafe Studio 2.0. https://www.devexpress.com/support/versions.xml#supported
I can confirm the above behaviour, however there is a workaround to get tests running again for 3.7.0-rc.1.
t.takeScreenshot()
anywhere it will still fail, so I had to add disableScreenshots: true
to testcaferc.jsoncsw1701 - are you using studio or open source test cafe?
I'm using open source testcafe
I am getting also same issue with Testcafe version 3.5.0 and tried with latest version 3.7.0 and 3.7.0-rc.1 also. I am stuck to run our daily automated test case. Could you provide any solution?
3.7.0-rc.2
fixes this issue for my Test Cafe use cases. The element interactions seem to behave the same as with 3.6.2
.
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.
3.7.0-rc.2
fixes this issue for my Test Cafe use cases. The element interactions seem to behave the same as with3.6.2
.
Thank you @Bayheck
3.7.0-rc.2
fixes this issue for my Test Cafe use cases. The element interactions seem to behave the same as with3.6.2
.
Thank you, It worked for me
3.7.0-rc.2
fixes the element interaction problem for me as well.
Thank you TestCafe team!
The fix seems to be working fine. However, I'm currently facing a dependency issue where certain packages require TestCafe to be a version "<1.0.0", and since RC2 is "3.7.0-rc.2", they are failing. Do we have an estimated release date for the official 3.7.0?
thanks in advance ! @Bayheck
Hello, At present, we are not ready to give any ETA.
Please stay tuned.
I will close this issue as it was fixed in the PR: https://github.com/DevExpress/testcafe/pull/8315
What is your Scenario?
I have seen multiple tickets related to errors caused by the latest stable version of Chrome (130), which I am also experiencing with TestCafe 3.6.2. In response, I upgraded to TestCafe RC1 3.7.0, which is supposed to address these issues.
However, it appears that Google Chrome is unable to interact with elements—specifically, it cannot type into or click on any elements. In contrast, switching to Firefox allows the tests to run without any issues.
Previously, everything was functioning correctly with TestCafe 3.6.2 and the earlier version of Chrome.
Note: The selectors may change depending on the language used in your machine.
What is the Current behavior?
Chrome is unable to interact with elements
What is the Expected behavior?
I should be able to interact with elements.
What is the public URL of the test page? (attach your complete example)
https://www.google.com/
What is your TestCafe test code?
Your complete configuration file
No response
Your complete test report
Screenshots
No response
Steps to Reproduce
see that firefox runs fine and chrome fails. using the scripts in the package.json
TestCafe version
3.7.0 rc1
Node.js version
No response
Command-line arguments
npm run chrome
Browser name(s) and version(s)
Chrome 130
Platform(s) and version(s)
No response
Other
No response