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

Testcafe became very unstable a few weeks ago #8184

Closed
rEtoAChM opened this issue May 7, 2024 · 2 comments
Closed

Testcafe became very unstable a few weeks ago #8184

rEtoAChM opened this issue May 7, 2024 · 2 comments
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@rEtoAChM
Copy link

rEtoAChM commented May 7, 2024

What is your Scenario?

Running latest testcafe with 'chromium:headless' within the testcafe/testcafe:latest docker image

What is the Current behavior?

We have the same issue as described here: #8145
But the described workaround doesnt work for us.

Running the tests with: 'testcafe chromium:headless tests.tsx' leads in 80% of runs to the described issue. Only workaround is to retry it as long as it works

Running tests with the suggested workaround: 'testcafe "chromium --headless=new" tests.tsx' leads to "Error: connect ECONNREFUSED 127.0.0.1:40603"

What is the Expected behavior?

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

What is your TestCafe test code?

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

TestCafe version

3.6.0

Node.js version

20.x

Command-line arguments

testcafe "chromium --headless=new" tests.tsx

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

@rEtoAChM rEtoAChM added the TYPE: bug The described behavior is considered as wrong (bug). label May 7, 2024
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label May 7, 2024
@Bayheck
Copy link
Collaborator

Bayheck commented May 8, 2024

Hello,

Please try running it with

testcafe chromium --headless=new

or

testcafe 'chrome --headless=new'

Please be aware of the quotes.

In TestCafe v3.6 and later, headless=new is default, and you can use chrome:headless again.

If these solutions don't fix the issue, please elaborate on it.

Running the tests with: 'testcafe chromium:headless tests.tsx' leads in 80% of runs to the described issue.

Do you mean you get the following error?

Error: Unable to open the "chrome:headless" browser due to the following error

@Bayheck Bayheck added STATE: Need clarification An issue lacks information for further research. and removed STATE: Need response An issue that requires a response or attention from the team. labels May 8, 2024
Copy link

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants