webdriver-manager

Unable to use protractor with chromedriver and selenium server directly

三世轮回 提交于 2020-01-03 05:52:21
问题 Recently I updated my protractor , webdriver-manager , chromedriver , selenium-server . After that I faced this problem: formerly we shared one protractor application in github with chromedriver and selenium-server in it. So others in my project can use it directly after downloaded this git project. We don't have seleniumAddress and directConnect in our protractor configuration file. It means we launched tests with local driver. But now update-config.json file was added to track chromedriver

Error: self signed certificate in certificate chain

百般思念 提交于 2020-01-03 04:13:45
问题 I can run the selenium server with fresh rebooting of my Windows 7. However if I kill the server and start it again, I will get this error. Sometimes doing webdriver-manager update--ignore_ssl may fix the problem, but most of time it won't fix. Any idea? I am running it on Windows 7 x64. C:\Users\...> webdriver-manager start --ignore_ssl events.js:163 throw er; // Unhandled 'error' event ^ Error: self signed certificate in certificate chain at TLSSocket.<anonymous> (_tls_wrap.js:1084:38) at

webdriver-manager update-config.json absolute paths

。_饼干妹妹 提交于 2019-12-25 07:46:56
问题 At webdriver-manager\selenium\update-config.json for "last" and "all" JSON parameters, I have absolute paths. How I can set relative paths to them? I tried "..\" and ".\" but it's not working. Any ideas? 回答1: Alright, so this is the design of update-config.json , what it is used for and why it is there. Write update-config.json during update When a user calls webdriver-manager update , the binaries are downloaded and renamed to include the version number. This allows a user to have multiple

webdriver-manager update with --alternate_cdn argument

倾然丶 夕夏残阳落幕 提交于 2019-12-24 19:17:08
问题 I want to do the below in my protractor-cucumber framework. I can not use public repo like googleapi.com as per org policy: webdriver-manager update --standalone=0 --chrome --alternate_cdn https://www.artifactrepository.xyz.net/artifactory/api/npm-teamdev/ Also this: webdriver-manager update --chrome=0 --standalone --alternate_cdn https://www.artifactrepository.xyz.net/artifactory/api/npm-teamdev/ But i always get this as response: C:\Users\ABCD\Desktop\JSProjects\protractor-cucumber

how to check what is causing webdriver-manager to fail

江枫思渺然 提交于 2019-12-24 09:26:05
问题 I am trying to execute this simple protractor example https://coryrylan.com/blog/introduction-to-e2e-testing-with-the-angular-cli-and-protractor and I am getting webpack: Compiled successfully. events.js:182 throw er; // Unhandled 'error' event ^ Error: connect ETIMEDOUT 123.123.123.123:443 at Object._errnoException (util.js:1024:11) at _exceptionWithHostPort (util.js:1046:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1185:14) As far as I could understand, this is an error caused

selenium webdriver manager update - npm

寵の児 提交于 2019-12-22 08:36:46
问题 I tried to update the selenium webdriver using the "webdriver-manager", but i get the error as, Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar Error: Got error Error: read ECONNRESET from https://selenium-release.storage.googleapis.com/2.48/selenium-server-standalone-2.48.2.jar fs.js:60 throw err; // Forgot a callback but don't know where? Use NODE_DEBUG=fs ^ Error: EPERM: operation not permitted, unlink

Protractor webdriver-manager chromedriver update

拥有回忆 提交于 2019-12-22 04:34:10
问题 There seems to be a issue with chromedriver 2.2 and the newest version of Chrome. This issue has to deal with the protractor not being able to send tab keys with 2.2. If I do webdriver-manager update, it does not update to the chromedriver 2.4. I did a hack where I downloaded chromedriver 2.4 exe myself and manually put it in the selenium folder, but that is not the best way to do this. How do you update protractor to use the latest version of Chromedriver 2.4? 回答1: I am having the same issue

When using Protractor 5.4.2, webdriver-manager downloads 2.46 which is not compatible with Chrome 74

左心房为你撑大大i 提交于 2019-12-18 06:56:39
问题 Protractor 5.4.2 uses webdriver-manager 12 which downloads Chromedriver 2.46. Chromedriver 2.46 supports Chrome 71-73 (see http://chromedriver.chromium.org/downloads). We need to download Chromedriver 74.0.3729.6. I also see that there is a webdriver-manager@13 that supports this. Should I use it with Protractor 5.4.2? 回答1: webdriver-manager@12.1.4 is fixed webdriver-manager released 12.1.4 which will download a max ChromeDriver version of 74. How to get it? do a fresh install of your node

Unable to launch multiple browser instances in Protractor

情到浓时终转凉″ 提交于 2019-12-11 10:01:34
问题 My config file is just launching 1 instance of chrome. I'm expecting it to open 2. This is my config multi capabilities. multiCapabilities: [ { browserName: 'chrome', logName: 'Chrome - Suite 1', shardTestFiles: false, maxInstances: 1, maxSessions: 1, specs: ['test/protractor/test.js'] }, { browserName: 'Chrome', logName: 'Chrome - Suite 2', shardTestFiles: false, maxInstances: 1, maxSessions: 1, specs: ['test/protractor/test2.js'] } ], Now I am facing the error as below: /usr/local/lib/node

Is `webdriver-manager start` necessary?

試著忘記壹切 提交于 2019-12-07 05:22:14
问题 I'm delving into the world of Protractor tests for AngularJS. All the tutorials recommend I execute the following after webdriver-manager update and prior to executing the test: webdriver-manager start According to the webdriver-manager man, the start command will 'start up the selenium server'. True enough, once I run the above command, I can see something at http://127.0.0.1:4444/wd/hub My questions is: is the above necessary? I currently run my tests without the above command. All I do is: