Skip to content

Use latest BrowserStack API version #19

Closed
Krinkle opened this Issue May 9, 2012 · 5 comments

2 participants

@Krinkle
Collaborator
Krinkle commented May 9, 2012

BrowserStack keeps their API versioned and both versions are available.

v2 has been released today: browserstack/api@1dce80e...v2

So lets try it soon and switch to v2 (after which we'll be able to extend the map to also map mobile browsers)

@sparshgupta

Support for BrowserStack API v2 would be very useful. Looking forward to it.

@sparshgupta

Do you have any information on timeline as to when this might be available. Having mobile browsers in this would be a very good feature and something I have been waiting for.

@Krinkle
Collaborator
Krinkle commented Oct 30, 2012

For now I'm awaiting BrowserStack v3 due to practical issues with v2.

It would require a fair amount of refactoring to change from v1 to v2, which would be wasted as soon as v3 comes along which is expected to be more user friendly and easier to work with.

@sparshgupta

Thanks for the update. I was looking around and couldn't find any information on BrowserStack v3. Do you have any knowledge on when is it expected to be out?

@Krinkle
Collaborator
Krinkle commented Nov 2, 2012

Not yet, but they are working on it.

Note that if you're looking for quick testing, their browser interface already supports all of this and one can join the swarm manually through there. That obviously doesn't help with automated testing, but it can help in the short term to periodically check up on how the test suite runs (since one can run a test suite in any browser, even if that browser isn't in the required browserSet for that job - by going to the /job/# page and clicking the test names).

@saiwong saiwong pushed a commit to saiwong/testswarm-browserstack that referenced this issue Nov 7, 2012
Sai Wong Updated to use browserstack v2 API
Updated to use the browserstack v2 API to allow for OS specific browser
workers. Also updated `map.js` to add previously unsupported browsers.
#19
373ff79
@Krinkle Krinkle closed this Nov 14, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.