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

Element Interaction Issues with TestCafe RC1 3.7.0 and Chrome 130 #8308

Closed
RafaelBeltranClip opened this issue Oct 21, 2024 · 17 comments
Closed
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@RafaelBeltranClip
Copy link

RafaelBeltranClip commented Oct 21, 2024

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?

import { Selector } from 'testcafe';


fixture `Bug Report: Form Submission Issue`
    .page `https://www.google.com/`; 

test('Search anything test', async t => {

    // Example selectors
    const searchInput = Selector('textarea[title="Buscar"]');
    const firstRecommendation = Selector('ul li').nth(0);

    await t
        .typeText(searchInput, 'find anything')
        .click(firstRecommendation);
});

Your complete configuration file

No response

Your complete test report

{
  "devDependencies": {
    "testcafe": "^3.7.0-rc.1"
  },
  "scripts": {
    "chrome": "testcafe chrome testcafe.js",
    "chrome:headless": "testcafe chrome:headless testcafe.js",
    "firefox": "testcafe firefox testcafe.js"
  }
}

Screenshots

No response

Steps to Reproduce

  1. npm run firefox
  2. npm run chrome

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

@RafaelBeltranClip RafaelBeltranClip added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 21, 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 21, 2024
@thomas-jakemeyn
Copy link

I am facing the same problem when running my tests locally. Nothing happens when clicking on checkboxes, buttons, etc.

  • Chrome 130
  • TestCafe 3.7.0-rc.1
  • MacOS Sonoma 14.6.1

@ManuelRauber
Copy link

ManuelRauber commented Oct 22, 2024

Same issue here. As soon as our build agents got a new image containing Chrome 130, all tests starting to fail.

  • Chrome 130
  • TestCafe 3.7.0-rc.1
  • Ubuntu 22.04.5

@thomas-jakemeyn
Copy link

Note that the problem does not seem to affect Edge 130 (which is also Chromium-based).

@yasinkocak
Copy link

yasinkocak commented Oct 22, 2024

Same issue with Chrome 130, we move to Edge as workaround, but our application is built for Chrome

  • Chrome 130
  • TestCafe 3.7.0-rc.1
  • MacOS Sonoma 14.7

Copy link

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.

@github-actions github-actions bot removed STATE: Need response An issue that requires a response or attention from the team. STATE: Issue accepted An issue has been reproduced. labels Oct 23, 2024
@kkapur5
Copy link

kkapur5 commented Oct 23, 2024

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

@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 23, 2024
@csw1701
Copy link

csw1701 commented Oct 23, 2024

I can confirm the above behaviour, however there is a workaround to get tests running again for 3.7.0-rc.1.

  • Disable native automation
  • Disable Screenshots and Video capture (I just commented them out in testcaferc.json). However if you use t.takeScreenshot() anywhere it will still fail, so I had to add disableScreenshots: true to testcaferc.json

@kkapur5
Copy link

kkapur5 commented Oct 23, 2024

csw1701 - are you using studio or open source test cafe?

@csw1701
Copy link

csw1701 commented Oct 23, 2024

csw1701 - are you using studio or open source test cafe?

I'm using open source testcafe

@rupesh1395
Copy link

rupesh1395 commented Oct 24, 2024

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?
image

@Bayheck Bayheck removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 24, 2024
@ksplache1
Copy link

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.

@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 24, 2024
rpoet-jh added a commit to eclipse-pass/pass-acceptance-testing that referenced this issue Oct 24, 2024
To fix chrome 130.x issue
DevExpress/testcafe#8308
@Bayheck
Copy link
Collaborator

Bayheck commented Oct 25, 2024

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.

@Bayheck Bayheck removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 25, 2024
@rupesh1395
Copy link

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.

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 with 3.6.2.

Thank you, It worked for me

@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 25, 2024
@thomas-jakemeyn
Copy link

3.7.0-rc.2 fixes the element interaction problem for me as well.

Thank you TestCafe team!

rpoet-jh added a commit to eclipse-pass/pass-acceptance-testing that referenced this issue Oct 25, 2024
To fix chrome 130.x issue
DevExpress/testcafe#8308
@RafaelBeltranClip
Copy link
Author

RafaelBeltranClip commented Oct 25, 2024

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

@Bayheck
Copy link
Collaborator

Bayheck commented Oct 28, 2024

Hello,
At present, we are not ready to give any ETA.

Please stay tuned.

@Bayheck Bayheck removed 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 29, 2024

I will close this issue as it was fixed in the PR: #8315

@Bayheck Bayheck closed this as completed Oct 29, 2024
@testcafe-need-response-bot testcafe-need-response-bot bot added STATE: Need response An issue that requires a response or attention from the team. and removed STATE: Need response An issue that requires a response or attention from the team. labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

9 participants