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

Unable to run Chrome with Node 22 #8355

Closed
AleksandrSubach opened this issue Dec 18, 2024 · 2 comments
Closed

Unable to run Chrome with Node 22 #8355

AleksandrSubach opened this issue Dec 18, 2024 · 2 comments
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@AleksandrSubach
Copy link

AleksandrSubach commented Dec 18, 2024

What is your Scenario?

Run TestCafe test example

What is the Current behavior?

ERROR Unable to open the "chrome:" browser due to the following error:

Error: connect ECONNREFUSED ::1:62666
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1615:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)

What is the Expected behavior?

Test pass

What is the public URL of the test page? (attach your complete example)

https://devexpress.github.io/testcafe/example/

What is your TestCafe test code?

import page from './page-model';

fixture `A set of examples that illustrate how to use TestCafe API`
    .page `https://devexpress.github.io/testcafe/example/`;

// Tests
test('Text typing basics', async t => {
    await t
        .typeText(page.nameInput, 'Peter') // Type name
        .typeText(page.nameInput, 'Paker', { replace: true }) // Replace with last name
        .typeText(page.nameInput, 'r', { caretPos: 2 }) // Correct last name
        .expect(page.nameInput.value).eql('Parker'); // Check result
});

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. Install Node 22
  2. Run test

TestCafe version

3.7.1

Node.js version

v22.12.0

Command-line arguments

testcafe chrome tests/test.js

Browser name(s) and version(s)

Chrome 131

Platform(s) and version(s)

Windows 10

Other

On Node 20 everything works as expected

@AleksandrSubach AleksandrSubach added the TYPE: bug The described behavior is considered as wrong (bug). label Dec 18, 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 Dec 18, 2024
@andreastorp
Copy link

I see the same issue when running testcafe in GitHub Actions using [windows-latest]. I also see the same error when running against edge.

I can confirm that the following "fixes" works for me:

  • Downgrade to Node 20
  • Run in [ubuntu-latest] instead
  • Run Firefox instead

@PavelMor25
Copy link
Collaborator

duplicate #8350

@PavelMor25 PavelMor25 added STATE: Duplicate An issues has been already reported in the other thread. and removed STATE: Need response An issue that requires a response or attention from the team. labels Dec 23, 2024
@PavelMor25 PavelMor25 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants