Currently I am using the below commands for start the server (using Mocha framework) during second command am getting an error message. Please find the below and share your input
1. npm install selenium-standalone#latest -g
2. selenium-standalone install
3. selenium-standalone start
Error Log: During "selenium-standalone install"
firefox install:
from:
https://github.com/mozilla/geckodriver/releases/download/v0.13.0/geckodriv
er-v0.13.0-win64.zip to:
C:\Users\xxuser\AppData\Roaming\npm\node_modules\selenium-standalone.selen
ium\geckodriver\0.13.0-x64-geckodriver
C:\Users\xxuser\AppData\Roaming\npm\node_modules\selenium-standalone\bin\seleni
um-standalone:105
throw err;
^ Error: Could not download https://selenium-release.storage.googleapis.com/3.0/IE
DriverServer_x64_3.0.1.zip
at Request. (C:\Users\xxuser\AppData\Roaming\npm\node_modules\se
lenium-standalone\lib\install.js:273:21)
It is either an issue with google not having the file in the right place or selenium-standalone having the wrong url. If you go to https://github.com/mozilla/geckodriver/releases/download/v0.13.0/geckodriver-v0.13.0-win64.zip
it will download a zip file.
if you go to https://selenium-release.storage.googleapis.com/3.0/IE%20DriverServer_x64_3.0.1.zip
you get:
NoSuchKeyThe specified key does not exist.
The issue isn't firefox (gecko) driver it is internet explorer's driver.
Related
I just want to install pakage in node js but when ever i am typing command on cmd prompt it says following
what to do?
I installed the #ui5/uiveri5 globally correctly. I download the ui-uiveri5 repository, then I go to directory of sample\apiTesting, and run the command
uiveri5 APITesting.spec
it report following error:
C:\src\open\ui5-uiveri5\sample\apiTesting\APITesting.spec.js:2
describe('APITesting', function() {
^
ReferenceError: describe is not defined
Please guide me on how to solve this issue. ( It report the same issue after I install the jasmine-node, mocha globally).
No need to install jasmine or mocha, just install uiveri5 globally with npm install #ui5/uiveri5 -g. Can you please try again, I merged a fix for another small issue. And with it, this sample starts fine.
When trying the Excel Addin Tutorial (https://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-quickstart-jquery?tabs=yeomangenerator) I get an error when running npm start :
> office-addin-taskpane-js#0.0.1 start D:\sheet_organizer
> office-addin-debugging start manifest.xml
Debugging is being started...
App type: desktop
Enabled debugging for add-in sheet_organizer. Debug method: 0
Starting the dev server... (webpack-dev-server --mode development)
The dev server is running on port 3000. Process id: 8456
Sideloading the Office Add-in...
Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: Unable to delete registry value "D:\sheet_organizer\manifest.xml" in key "HKCU\SOFTWARE\Microsoft\Office\16.0\Wef\Developer".
ProcessUncleanExitError: DELETE command exited with code 1:
Error: can't find the key or the value
I check manually the key. There is a Developper>05c2e1c9-3e1d-406e-9a91-e9ac64854143 folder
With UseDirectDebugger, UseLiveReload and UseWebDebugger
So the key exist. Don't understand why it is not working.
Yes, this issue was fixed. OfficeDev/Office-Addin-Scripts#215
Please get the latest version of office-addin-debugging.
There are a couple of ways to do this.
1- npm update --dev can update all packages according to semver. (You can see outdated packages using npm outdated --long.)
2- You could update office-addin-debugging package using npm install -D office-addin-debugging.
Ref:https://github.com/OfficeDev/office-js-docs-pr/issues/1321
I need to install and use Protractor / Selenium on the machine without Internet access.
To do that, I've tried to download all needed files and copy them to the destination machine.
On my machine (with Internet access)
I installed Protractor and Selenium webdriver with the following command:
npm install -g protractor
webdriver-manager update
On destination machine (without Internet access)
I copied all files from the location returned by npm config get prefix to the computer without Internet access.
Then I executed following command on the machine without Internet access:
npm --cache-min 9999999 install -g protractor
which seems to succeed.
However, when I try to execute webdriver-manager start command, I receive following error message:
events.js:183
throw er; // Unhandled 'error' event
^
Error: getaddrinfo ENOTFOUND chromedriver.storage.googleapis.com
chromedriver.storage.googleapis.com:443
at errnoException (dns.js:50:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)
I receive the same error when executing webdriver-manager update (as in this case: webdriver-manager start: Error: connect ETIMEDOUT)
Question
What am I doing wrong? How should I properly setup Protractor and webdriver on the machine without Internet access?
Because webdriver-manager start will look up the latest version number of selenium-server.jar and webdriver binaries through internet no matter they are already exists on local.
But webdriver-manager not supply cmd option to disable the looking up.
The quick way is to run the java cmd behind webdriver-manager start directly to skip the looking up.
java
-Dwebdriver.chrome.driver=C:\Tools\npm-global\node_modules\webdriver-manager\selenium\chromedriver_2.38.exe
-Dwebdriver.gecko.driver=C:\Tools\npm-global\node_modules\webdriver-manager\selenium\geckodriver-v0.20.1.exe
-jar C:\Tools\npm-global\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.11.0.jar
-port 4444
The complex way is to change webdriver-manager code or setup a mirror on local and use cmd option: --alternate_cdn and point it to your local mirror url. ( I didn't verify this can work, get it after read some source code)
I get error PhantomJS does not exist at '/usr/local/phantomjs/bin/phantomjs on the terminal upon running the tests (npm tests) for Cloudboost Javascript SDK repo. Any idea how to fix this?
Install PhantomJS from here, and create a symlink of the downloaded folder in your /usr/local/ directory. Run the command npm test again and that error would be gone.