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

Add option to override defaultArgs for chrome #8382

Open
sntherr102 opened this issue Feb 18, 2025 · 4 comments
Open

Add option to override defaultArgs for chrome #8382

sntherr102 opened this issue Feb 18, 2025 · 4 comments
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: enhancement The accepted proposal for future implementation.

Comments

@sntherr102
Copy link

What is your Scenario?

Testcafe version: 3.7.1
Chrome version: 133

Chrome is not starting when running tests in 3.7.1 version, which is caused by --enable-automation option. I assume this option is in conflict with company policy for chrome. When --enable-automation option is removed from defaultArgs the chrome starts.

What are you suggesting?

Since there in not chrome parameter to reverse this setting, please provide an option to override it from Testcafe level.

What alternatives have you considered?

I can remove this flag when running tests locally, but running tests on remote machine is problematic.

Additional context

No response

@sntherr102 sntherr102 added the TYPE: enhancement The accepted proposal for future implementation. label Feb 18, 2025
@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 Feb 18, 2025
@Bayheck
Copy link
Collaborator

Bayheck commented Feb 24, 2025

Hello,
Сould you please elaborate on:

I assume this option is in conflict with company policy for chrome

What error did you encounter?

@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 Feb 24, 2025
@sntherr102
Copy link
Author

No error, I just get this message after chrome fails to start:

ERROR Cannot establish one or more browser connections.
1 of 1 browser connections have not been established:
- chrome:userProfile

Hints:
- Increase the Browser Initialization Timeout if its value is too low (currently: 2 minutes for local browsers and 6 minutes for remote browsers). The timeout determines how long TestCafe waits for browsers to be ready.
- The error can also be caused by network issues or remote device failure. Make sure that your network connection is stable and you can reach the remote device.

@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 Feb 25, 2025
@github-actions github-actions bot removed the STATE: Need clarification An issue lacks information for further research. label Feb 25, 2025
@aleks-pro
Copy link
Contributor

Hello @sntherr102 ,

Thank you for reporting the issue. We will remove the --enable-automation option from the defaultArgs. We will add this fix in the next TestCafe patch release.

@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 Feb 28, 2025
@aleks-pro aleks-pro self-assigned this Mar 21, 2025
@aleks-pro
Copy link
Contributor

Hello @sntherr102 ,

We took a closer look and found out that removing --enable-automation will lead to regression for specific usage scenarios with the resize window action. So, we cannot just remove it from the defaultArgs as we decided to do earlier.

Could you please explain in greater detail why this option is in conflict with your company policy? The flag indicates that the browser is under automation and this is what TestCafe does. The flag changes browser behavior and fixes multiple issues with the latest Chrome versions.

@aleks-pro aleks-pro added the STATE: Need clarification An issue lacks information for further research. label Mar 21, 2025
@aleks-pro aleks-pro removed their assignment Mar 21, 2025
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: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

3 participants