-
Notifications
You must be signed in to change notification settings - Fork 2.3k
feat(webdriver): extract webdriver-manager into a separate node module #3068
Conversation
So much 👏 🎊 This is slightly OT (feel free to ignore if i've missed out on a conversation elsewhere), but have we considered asking the |
Nit: commit should say "extract webdriver-tool into..." re: @NickTomlin Also, we are the |
We're discussing with the owner of |
@sjelin ah yeah I should have been clearer, I mean the community npm webdriver-manager fork Glad to hear we are talking with the NPM owner. Hopefully we can work that out! |
Name change from webdriver-tool to webdriver-manager. Updating this pr to reflect this. Should not be merged until we publish to npm... also shouldn't work since |
8452bdb
to
b79d915
Compare
b79d915
to
77c78aa
Compare
386f7bd
to
0536aec
Compare
531d409
to
bc05cc4
Compare
browserStack tests are failing which needs to be addressed. |
bc05cc4
to
3bd0252
Compare
8fb2e3c
to
1445c4e
Compare
bee998d
to
99eb425
Compare
99eb425
to
0cd63d7
Compare
@@ -45,9 +45,10 @@ Clone the github repository: | |||
npm install | |||
cd .. | |||
|
|||
Start up a selenium server. By default, the tests expect the selenium server to be running at `http://localhost:4444/wd/hub`. A selenium server can be started with `webdriver-manager`. | |||
Start up a selenium server. By default, the tests expect the selenium server to be running at `http://localhost:4444/wd/hub`. A selenium server can be started with [webdriver-manager](https://github.com/angular/webdriver-manager). |
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.
Maybe add something like: "which is included in bin/webdriver-manager"?
We should mention in the commit description that this will change the filenames by giving everything versions. |
8994bd0
to
1532aec
Compare
1532aec
to
99ba59b
Compare
|
closes #607, closes #2402