There are many scenarios where these options, especially directDomains or noSslBumpDomains, would be really useful for the consumer of this package to specify. At the moment, these are hard-coded: https://github.com/DevExpress/testcafe-browser-provider-saucelabs/blob/master/src/index.js#L187-L189 , which makes it impossible for me to test web socket functionality due to the inability to specify noSslBumpDomains.
My proposal is that we use a similar mechanism that this package already does for SAUCE_CAPABILITIES_OVERRIDES_PATH, perhaps called SAUCE_CONNECT_OVERRIDES_PATH, where consumers can specify their overrides.
Happy to open a pr for the approach outlined above or an alternative that the maintainers think is better.
There are many scenarios where these options, especially
directDomains
ornoSslBumpDomains
, would be really useful for the consumer of this package to specify. At the moment, these are hard-coded: https://github.com/DevExpress/testcafe-browser-provider-saucelabs/blob/master/src/index.js#L187-L189 , which makes it impossible for me to test web socket functionality due to the inability to specifynoSslBumpDomains
.My proposal is that we use a similar mechanism that this package already does for
SAUCE_CAPABILITIES_OVERRIDES_PATH
, perhaps calledSAUCE_CONNECT_OVERRIDES_PATH
, where consumers can specify their overrides.Happy to open a pr for the approach outlined above or an alternative that the maintainers think is better.