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

Open
RafaelBeltranClip opened this issue Oct 21, 2024 · 4 comments
Open
Labels
STATE: Need response An issue that requires a response or attention from the team. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need response An issue that requires a response or attention from the team. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

4 participants