Skip to content

Instantly share code, notes, and snippets.

@jfsiii

jfsiii/gist:5580949

Created May 15, 2013 01:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jfsiii/5580949 to your computer and use it in GitHub Desktop.
Save jfsiii/5580949 to your computer and use it in GitHub Desktop.
Download ZIP
Why use the BrowserStack Automated Testing API?
Raw
gistfile1.txt
I think I need an overview of what the BrowserStack Automated Testing API is for. I'm struggling to understand the use case(s). I can request a list of allowed browsers then, based on those, create a worker which then ... does what?
I've been able to successfully create a worker (it went from "queued" to "running" status), but what's next? Specifically, how can I view this worker (the page running in the browser, not just its status).
Right now I'm simply told that one was created, but it seems academic because I don't know how to view it live or after the fact.
Can you help fill in the gaps? I'm sure I'm missing something.
Thanks,
John
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment