If you are following protractor or practicing then you might have noticed that you do not install or point the driverservers, and jar files in our conf file.
If you are from Selenium background then you might have used this parameter by setting the system property
System.setProperty("webdriver.chrome.driver", "PATH to exe file")
We will be using the
npm install webdriver-manager to fetch all the required file for the execution. But if you notice the "
The webdriver-manager folder, but as of now, you can only see webdriver-manager files, not a selenium folder.
npm install webdriver-manager will not fetch the files, It just enables us to fetch those.
The Update command will fetch all the required files for the protractor execution.
I know the obvious question in your mind. Why are you showing the global installation when you have not used -g at all.?
The above command will install globally because you are accessing the
webdriver-manager and it is global, not local.
Local installation of these drivers are not possible so you got to depend on the global installation.
You can get the all these commands by setting help command
The above commands will be followed by the
webdriver-manager <command> [options] webdriver-manager update --gecko --proxy="proxyurl"
This error occurs when protractor was not able to install webdriver-manager, if you get below error install the webdriver-manager explicitly.
npm install webdriver-manager
By default, the selenium server will run on http://localhost:4444/wd/hub. This command was used in very earlier versions but Now using this command has no use.