Skip to content
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

Closed
hppycoder opened this issue May 10, 2013 · 6 comments
Closed

Integration with Selenium or Sahi #542

hppycoder opened this issue May 10, 2013 · 6 comments

Comments

@hppycoder
Copy link

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.

@vojtajina
Copy link
Contributor

Not sure I understand what you mean. It sounds like you are asking for
webdriver launcher, that would allow starting any browser throw
webdriver/selenium, right ? If so, the answer is yep, go for it. I
think implementing such a launcher should be pretty simple.

There is already an issue to create a specific launcher for SauceLabs #357
and BrowserStack #96.

On Fri, May 10, 2013 at 6:46 AM, Chad Smith notifications@github.comwrote:

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/542
.

@hppycoder
Copy link
Author

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.

@aparkinson
Copy link

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

@hppycoder
Copy link
Author

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.

@vojtajina
Copy link
Contributor

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.

@vojtajina
Copy link
Contributor

I meant, a repo with you guys as maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants