-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Integration with Selenium or Sahi #542
Comments
Not sure I understand what you mean. It sounds like you are asking for There is already an issue to create a specific launcher for SauceLabs #357 On Fri, May 10, 2013 at 6:46 AM, Chad Smith notifications@github.comwrote:
|
I've been using the past few days to look into how I could go about creating my own webdriver for this. Would you please give me some hints on how you would start putting a external communication mechanism in place? I know that we aren't the only ones coming up to this issue and think that it would be really cool to get implemented and could open the doors for other drivers out there. |
Myself and @jbastow have created a Remote Webdriver Launcher plugin (https://github.com/hindsightsoftware/karma-webdriver-launcher) but it depends on PR #533 We just need a little guidance on how we can contribute this to Karma |
I have looked at what you guys have done and it's really great! I see it depends on PR #533 as well so hopefully that gets accepted soon and a stable build could come from it incorporating your changes. I think this really opens Karma up to a lot of great use cases. |
I'm closing this, as I think the webdriver launcher is exactly. @aparkinson @jbastow that is awesome, ping me on email or something, I'm happy to create a repo for the webdriver launcher under karma-runner org. The #533 has been merged, I hope to push a new release to npm this week. |
I meant, a repo with you guys as maintainers. |
Looking back through the issues here and I am not seeing anyone bring this up before.
What would it take to get the runner to go out to Selenium and/or Sahi? That way a CI build system could thread through any number of browsers or browser stacks and get the results of failures.
The text was updated successfully, but these errors were encountered: