Allow to apply Chrome arguments via browser aliases about testcafe-browser-provider-saucelabs HOT 9 CLOSED

Thank you for your inquiry. testcafe-browser-provider-saucelabs doesn't support passing Chrome command-line options to cloud browsers yet. But since it uses Selenium to control browsers, likely you don't need the --autoplay-policy=no-user-gesture-required flag, try to remove it and run your tests with saucelabs:chrome.

from testcafe-browser-provider-saucelabs.

Hi, when testing against HTTPS sites we always need to suppress the browsers insecure certificate warning (in Chrome using "--allow-insecure-localhost"). I am lead to believe that this can only be done on the command line when you start the browser. Hence the limitation that @bassihani raises might be a significant issue for HTTPS site testing.

from testcafe-browser-provider-saucelabs.

Hi @gmarsh-cl,

Thank you for sharing your experience. Did you try to use the SAUCE_CAPABILITIES_OVERRIDES_PATH environment variable? You can create your custom SauceLab configuration file (like the one below) and define a path to it via SAUCE_CAPABILITIES_OVERRIDES_PATH.

"chromeOptions": {
  "args": [
    "allow-insecure-localhost",

    "start-maximized",
    "disable-webgl",
    "blacklist-webgl",
    "blacklist-accelerated-compositing",
    "disable-accelerated-2d-canvas",
    "disable-accelerated-compositing",
    "disable-accelerated-layers",
    "disable-accelerated-plugins",
    "disable-accelerated-video",
    "disable-accelerated-video-decode",
    "disable-gpu",
    "disable-infobars",
    "test-type"
  ]
}

To be honest, I didn't try it myself, but it should work according to the docs.

from testcafe-browser-provider-saucelabs.

Thank you @alexey-lin I will try this out and report back.

from testcafe-browser-provider-saucelabs.

Hi @alexey-lin after your suggestion I have managed to get SauceLabs to accept the args which is great. Strangely though, as you can see from my screenshot, SauceLabs seems to have ignored it. Or perhaps this is an issue with Chrome 79?

from testcafe-browser-provider-saucelabs.

@gmarsh-cl
As you can see in the screenshot, TestCafe does not use the hostname localhost in your case. Try to use the ignore-certificate-errors Chrome flag instead.

from testcafe-browser-provider-saucelabs.

@Dmitry-Ostashev excellent, thank you so much. That resolved the problem. For anyone else out there suffering with the same issue, on Sauce Labs you can pass in the following for Firefox and IE to get around the untrusted certificate issues:

(FF)
{
"acceptInsecureCerts": true,
"moz:firefoxOptions": {
"prefs": {
"network.websocket.allowInsecureFromHTTPS": true
}
}
}

and (IE)

{
"acceptInsecureCerts": true
}

from testcafe-browser-provider-saucelabs.

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

from testcafe-browser-provider-saucelabs.

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

from testcafe-browser-provider-saucelabs.