-
Notifications
You must be signed in to change notification settings - Fork 18
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
Provide a dynamic list of Sauce browsers to enable #1
Comments
I'm working on improving our browser list right now to make it provide both Se1 and WebDriver browsers. |
currently allows to cherry pick what flavor you want from the result of rest/v1/info/browsers what capabilities are currently on for the node is kept as a list of md5 of those capabilities so that each time one of them changes, the node config can be updated accordingly. se1 or se2 protocol for the node will be necessary for the CapabilityMatcher implementation, not for the dynamic list. |
Alright, just finished improving the Sauce REST API to better reflect the list of available browsers based on the backend technology to use: There's also a full list available: |
FWIW, the split of browsers needs to be done by backend as Sauce supports some browsers in one backend that are not supported in the other, for example Safari is currently Se1 only, iPad is currently WebDriver only. |
I just found the list provided by our REST API wasn't accurate. I'm working on a rewrite of how Sauce handles browsers to make a fix in our end for this. |
Sauce should provide this list through a rest API and the plugin should pull it periodically
The text was updated successfully, but these errors were encountered: