No easy way to wait for webdriver start
See original GitHub issueI’ve tried to set up Protractor with Grunt via grunt-protractor-runner. The problem is that I want to be able to run all that automatically and:
- Protractor needs
webdriver start
to be run manually - There is apparently no way to tell when
webdriver
is ready.
This creates a problem as my grunt testE2E
command has to start webdriver somehow to be able to run Protractor tests. webdriver start
cannot be run in a synchronous mode since it blocks but it also cannot be run in the background as then Protractor doesn’t wait until it’s fully initialized.
Is there any way around that? I want to test in both Firefox & Chrome so I need the Seleniun server for that.
EDIT: I assume there is no Firefox driver available that would allow one to skip Selenium for this browser as well? (i.e. it’s not only an issue of implementing support in Protractor but that needed software is missing?)
Issue Analytics
- State:
- Created 10 years ago
- Comments:6 (5 by maintainers)
Top GitHub Comments
Protractor would start a selenium-webdriver server automatically if you omit the
seleniumAddress
config option 😉 so all is needed is a config file and to runprotractor e2e.conf.js
that’s it.Nice!