-
Notifications
You must be signed in to change notification settings - Fork 25
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
Please release 0.2.530 #29
Comments
Hi Ian, tests are failing so have not published it. Is the head working for you? I'm not using selenium for my day job at the moment. |
The main issue was supporting Phantom 2, I could reverse that change and publish with latest selenium |
I haven't actually tried any thing other than what's on npm. I just know that the version on npm ships with a version of the selenium jar that is no longer compatible with firefox. We only use grunt-selenium-webdriver for local testing, not our CI setup, so it's more of a huge inconvenience than a complete blocker. That said, it would be immensely helpful to have the latest selenium jar available. As a longer-term solution, this sort of thing might be avoidable if consumers could supply a path to their own jar if the default doesn't work. |
Any updates?.. Newer versions of Grunt not being supported is a huge blocker :( |
+1 |
It's been nearly a year since this has been updated, so I'm pretty sure someone's going to have to fork it to get a fix out. I've switched to webdriver.io and largely pulled grunt out of most of my flows, otherwise I would've last summer. |
Sorry I don't use this, it someone supplies a fix then I'll put it live and / or transfer ownership. |
Looks like package.json got updated, but npm still shows 0.2.482 as the latest version
The text was updated successfully, but these errors were encountered: