-
Notifications
You must be signed in to change notification settings - Fork 675
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
Comments
Hello,
What error did you encounter? |
No error, I just get this message after chrome fails to start:
|
Hello @sntherr102 , Thank you for reporting the issue. We will remove the |
Hello @sntherr102 , We took a closer look and found out that removing 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. |
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
The text was updated successfully, but these errors were encountered: