BrowserStack Legacy capability vs BS SDK aka WDIO has (not really) BS support out of the box #14527
dprevost-LMI
started this conversation in
General
Replies: 1 comment 1 reply
-
There is no plan at all. The @webdriverio/browserstack folks have worked on several improvements to the BS service which will help with integrating WebdriverIO into BS but WebdriverIO is currently not planning to "support" anything proprietary.
All WebdriverIO <> BrowserStack integration parts are owned by @webdriverio/browserstack folks. The WebdriverIO core team can not speak to any of that. I asked them to update the documentation, see #14456 (comment). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When we first started a year ago with WDIO, one of our criteria was to have the support of BrowserStack, so we are pleased that this is still supported.
We have integrated everything and generated a
conf.tsfile with capabilities, and it is still working fine. However, a couple of months ago, we started hearing that we need to use the BrowserStack SDK, and we were relying on theWebdriverIO has BrowserStack support out of the box, so we were "waiting" for WebdriverIO to move from Legacy capabilities to the new BrowserStack SDK.At the same time, I do not hear anything about the support for BrowserStack SDK. They have also deprecated some capabilities on their website in favour of their SDK (see below)
At the same time, the WDIO docs still state that BS is out of the box, while now with this SDK, it is not. Moreover, the document does not mention the SDK or the Legacy capabilities.
In short:
Beta Was this translation helpful? Give feedback.
All reactions