Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Provide a dynamic list of Sauce browsers to enable #1

santiycr opened this Issue Apr 23, 2012 · 5 comments


None yet
2 participants

santiycr commented Apr 23, 2012

Sauce should provide this list through a rest API and the plugin should pull it periodically

@santiycr santiycr was assigned Apr 24, 2012


santiycr commented Apr 24, 2012

I'm working on improving our browser list right now to make it provide both Se1 and WebDriver browsers.


freynaud commented Apr 24, 2012

currently allows to cherry pick what flavor you want from the result of rest/v1/info/browsers
capabilities are cached to avoid calling the Sauce api too often.

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.


santiycr commented Apr 27, 2012

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:


santiycr commented Apr 27, 2012

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.


santiycr commented May 22, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment