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

Chrome does not start correctly in headless mode on Windows 11 (Chrome Version 129.0.6668.90) #8294

Closed
GregorBiswanger opened this issue Oct 4, 2024 · 1 comment
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@GregorBiswanger
Copy link

What is your Scenario?

I am running tests in headless mode using TestCafe version 3.6.2 and Google Chrome version 129.0.6668.90 on Windows 11.

What is the Current behavior?

When I execute the following command:
npx testcafe chrome:headless e2e

a blank, white Chrome window opens, but no content is displayed. The test seems to hang without progressing.

I also tried running the new headless mode using the following command:
npx testcafe "chrome:--headless=new" e2e

This results in the same issue. The only command that works is:
npx testcafe "chrome:--headless=old" e2e

What is the Expected behavior?

The tests should run in headless mode with Chrome, displaying the page content without opening a visible Chrome window.

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

N/A (this issue occurs in a local project).

What is your TestCafe test code?

Basic e2e test structure.

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. Run npx testcafe chrome:headless with Google Chrome version 129.0.6668.90 on Windows 11.
  2. Observe that a blank, white window opens and the test hangs.

TestCafe version

3.6.2

Node.js version

No response

Command-line arguments

npx testcafe chrome:headless e2e

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

@GregorBiswanger GregorBiswanger added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 4, 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 4, 2024
@PavelMor25
Copy link
Collaborator

Duplicate #8287

@testcafe-need-response-bot testcafe-need-response-bot bot removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 10, 2024
@PavelMor25 PavelMor25 added the STATE: Duplicate An issues has been already reported in the other thread. label Oct 10, 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

2 participants