-
-
Notifications
You must be signed in to change notification settings - Fork 198
Replace chromedriver-helper with webdrivers #1038
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
Conversation
ab0f3d4 to
b50acd1
Compare
|
@notapatch do you want to give this a rebase now that it's prerequisite PR has been merged in? |
b50acd1 to
91c6420
Compare
|
Rebased as requested. This should be tested on your local system as it changes your development tooling - It would reassure if another developer had run it ok. This changes one way of installing chromedriver with another - there may be a teething issue, I hope not, but after that the tests are still calling Chromedriver which will now be kept up to date - rather than manually updating. Testing on a local development system without mergingAssuming
From the terminal:Any problems? This is an important commit because the likelihood of the deprecated chromdriver-helper breaking all builds increases with time. |
91c6420 to
35a3a5e
Compare
fbad2f4 to
ce4dbab
Compare
fae664e to
18e70f7
Compare
|
This one would close two issues and was tested in Docker by biggianteye - I think you were of a mind to close the issue when he agreed it was ok ... which he did The only place it possibly irritate anyone would be non-docker developers - and I don't personally remember a problem. Meanwhile we've been running a deprecated driver for a few months and we will have a crash at some point if we don't get off it. |
045fab7 to
9fba4af
Compare
|
@matyikriszta - with this commit we know docker is painless. I can put an issue out saying would a native user contact me - and if nobody contacts me we can merge this time next week? |
|
I applied the changes requested here in my local installation of the master branch. When I run the bin/drake command, I get a webdrivers error about being unable to find the latest point release. I get the following error message: @notapatch It would be easier to work with this pull request if it were even with the master branch instead of 23 commits behind. Everyone else: Is there some reason that I'm not seeing a codebar:webdrivers branch? |
|
@jhsu802701 - sorry for the misunderstanding. It's up to date. I'm seeing the same issue. Update:the issue comes from the Dockerfile installing an "edge" version of the browser (which they call unstable). This version is ahead of the drivers and it errors out. PR to fix this |
|
@notapatch I tested this and it worked correctly for me, did not experience the issue reported by @jhsu802701 (although I do not have Docker running at the moment and never attempted to install the app via Docker). This PR needs a rebase but I'm happy to merge after. I've merged #1149 in already. |
- Why are we changing?
Chromedriver is used to automate our browser tests.
- Chromedriver implements the webdriver standards for
automated testing of webapps for Chrome.
https://chromedriver.chromium.org/
Chromedriver-helper had the task of installing Chromedriver
for us and making sure the exe was in the Gem path. We could
have installed it ourselves but this was easier.
chromedriver-helper is no longer maintained as of 2019-03-31
we
- flavorjones/chromedriver-helper#83
- What are we changing to?
Webdrivers is now responsible for downloading drivers - in our
case chromedriver.
- webdrivers has selenium-webdrivers as dependency removing from
Gemfile and changing Capabyara to require 'webdrivers'
- What are the differences?
Webdrivers can do the same as Chromedrivers (superset of
functionality) - but can also do other drivers and it does it
automatically - with chromedriver-helper you had to automated
it by hand - this should help avoid problems with running
tests with old drivers.
d5718af to
4be0a90
Compare
|
@matyikriszta - rebased! I did not know you were native/non-docker? Well that's the final test and we can move to the industry standard webdrivers. |
matyikriszta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Why are we changing?
Chromedriver is used to automate our browser tests.
- Chromedriver implements the webdriver standards for
automated testing of webapps for Chrome.
https://chromedriver.chromium.org/
Chromedriver-helper had the task of installing Chromedriver
for us and making sure the exe was in the Gem path. We could
have installed it ourselves but this was easier.
chromedriver-helper is no longer maintained as of 2019-03-31
- NOTICE: Ending support for this gem flavorjones/chromedriver-helper#83
What are we changing to?
Webdrivers is now responsible for downloading drivers - in our
case chromedriver.
webdrivers has selenium-webdrivers as dependency removing from
Gemfile and changing Capabyara to require 'webdrivers'
What are the differences?
Webdrivers can do the same as Chromedrivers (superset of
functionality) - but can also do other drivers and it does it
automatically - with chromedriver-helper you had to automated
it by hand - this should help avoid problems with running tests
with old drivers.
Closes issue #1012