mouseMove is not working in firefox with the latest versions of Firefox, geckodriver, and protractor. Same code works fine for chrome 77.
I have the following environment:
Node: v10.16.3
Protractor: 5.4.2
Geckodriver: v0.25.0
firefox: 69.0.1 (64-bit)
browser.actions().mouseMove(element(by.xpath('//app-admin-panel/div/div/div/div[2]/table/tbody/tr/td[1]'))).perform();
This code snippet should hover over the specified element, but it throws the following error:
Message:
Failed: HTTP method not allowed
Stack:
WebDriverError: HTTP method not allowed
at parseHttpResponse (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:536:11)
at doSend.then.response (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: mouseMove
at Driver.schedule (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:807:17)
at actions.map.action (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:124:23)
at Array.map (<anonymous>)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:123:29
at TaskQueue.execute_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3084:14)
at TaskQueue.executeNext_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3067:27)
at asyncRun (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2927:27)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:668:7
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: ActionSequence.perform
at ActionSequence.perform (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\actions.js:122:33)
at UserContext.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:39:207)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:112:25
at new ManagedPromise (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1077:7)
at ControlFlow.promise (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2505:12)
at schedulerExecute (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:95:18)
at TaskQueue.execute_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3084:14)
at TaskQueue.executeNext_ (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:3067:27)
at asyncRun (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2974:25)
at C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:668:7
From: Task: Run it("Make a Copy of Dashboard") in control flow
at UserContext.<anonymous> (C:\Users\Hassan Sohail\AppData\Roaming\npm\node_modules\protractor\node_modules\jasminewd2\index.js:94:19)
From asynchronous test:
Error
at Suite.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:38:5)
at Object.<anonymous> (E:\Office\Protractor\Wallboard\Smoketest.js:2:1)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
4 specs, 1 failure
Finished in 21.836 seconds
[11:41:20] I/launcher - 0 instance(s) of WebDriver still running
[11:41:20] I/launcher - firefox #01 failed 1 test(s)
[11:41:20] I/launcher - overall: 1 failed spec(s)
[11:41:20] E/launcher - Process exited with error code 1
It's a known issue (not sure if they fixed it yet) for FF.
I suggest you to use this https://www.npmjs.com/package/protractor-firefox-support
solved by updating direct connect value to false in protractor config
in case of chrome set it to true for local testing
directConnect: false
Related
This is what I get in the stack trace from launching chrome: Cypress version is 7.3.:
Title: Error launching browser
Message: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually indicates there was a problem opening the Chrome browser.
The CDP port requested was 29079.
Error details:
Error: connect ECONNREFUSED 127.0.0.1:29079
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
Stack trace:
Error: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
This usually indicates there was a problem opening the Chrome browser.
The CDP port requested was [33m29079[39m.
Error details:
Error: connect ECONNREFUSED 127.0.0.1:29079
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
at get (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\errors.js:988:15)
at Object.throwErr [as throw] (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\errors.js:1006:9)
at C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\lib\browsers\protocol.js:106:21
at tryCatcher (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:725:18)
at _drainQueueStep (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:93:12)
at _drainQueue (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:86:9)
at Async._drainQueues (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\giannia\AppData\Local\Cypress\Cache\7.3.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:15:14)
at processImmediate (internal/timers.js:461:21)
I have spoken to the support team and they currently do not have any protocols in place that would block cypress from launching chrome. I have also looked at an earlier solution in stack overflow where you go into ext/files to comment out the localhost address but still to ano avail. Can anyone please help??
I'm trying to run a server with Express.js and each time I try to run it on port 1000 I get the following message:
events.js:292
throw er; // Unhandled 'error' event
^
Error: listen EACCES: permission denied 0.0.0.0:1000
at Server.setupListenHandle [as _listen2] (net.js:1301:21)
at listenInCluster (net.js:1366:12)
at Server.listen (net.js:1452:7)
at Function.listen (/Users/orensayag/Documents/johnBryce/26 - 210421/hw/node_modules/express/lib/application.js:618:24)
at Object.<anonymous> (/Users/orensayag/Documents/johnBryce/26 - 210421/hw/index.js:6:5)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1345:8)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
code: 'EACCES',
errno: -13,
syscall: 'listen',
address: '0.0.0.0',
port: 1000
}
I've also heard that Macs have a problem with running on this port, and that in Windows it runs as expected.
Why can't my Mac run a server on port 1000?
For ports lower than 1024 you need to be root. You are getting access denied because the user starting the process does not have a root access.
Everytime I'm trying to publish an app with sidekick I'm getting the same error:
--> starting at object with constructor 'Error'
--- property 'errors' closes the circle
at JSON.stringify (<anonymous>)
at process.target._send (internal/child_process.js:778:25)
at process.target.send (internal/child_process.js:676:19)
at MessageService.sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/message-service.js:34:21)
at sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:13:24)
at sendErrorMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:19:9)
at /opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:36:17
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at emitUnhandledRejectionWarning (internal/process/promises.js:141:15)
at processPromiseRejections (internal/process/promises.js:203:11)
at processTicksAndRejections (internal/process/task_queues.js:94:32)
(CLI) (node:17346) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'Error'
--- property 'errors' closes the circle
at JSON.stringify (<anonymous>)
at process.target._send (internal/child_process.js:778:25)
at process.target.send (internal/child_process.js:676:19)
at MessageService.sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/message-service.js:34:21)
at sendMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:13:24)
at sendErrorMessage (/opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:19:9)
at /opt/NativeScript Sidekick/resources/app.asar.unpacked/shared/child-process/child-helpers.js:36:17
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:17346) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
at emitDeprecationWarning (internal/process/promises.js:153:11)
at processPromiseRejections (internal/process/promises.js:205:13)
at processTicksAndRejections (internal/process/task_queues.js:94:32)
Version: 1.19.2-v.2019.11.18.2 (latest)
NativeScript CLI version: 6.2.2
CLI extension nativescript-cloud version: 1.19.3
CLI extension nativescript-starter-kits version: 0.3.5
node: v12.13.1
I've tried downgrade the node verson, to 10.12.0, still getting the same error
Helo Friends,
I am trying to do a POC with Nightwatch.js on windows machine and ended up getting the below error. Could you please help me in resolving this issue.
Starting selenium server... started - PID: 12796
Error: No source folder defined. Check configuration.
at Function.Runner.readPaths (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\run.js:192:11)
at Runner.runner [as run] (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\run.js:235:10)
at CliRunner.runner (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\cli\clirunner.js:443:23)
at C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\cli\clirunner.js:395:12
at SeleniumServer.onStarted (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\cli\clirunner.js:354:9)
at SeleniumServer.checkProcessStarted (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\selenium.js:152:10)
at SeleniumServer.onStderrData (C:\Users\user_abc\IdeaProjects\nightwatch-cucumber-example\node_modules\nightwatch\lib\runner\selenium.js:132:8)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:607:20)
INFO Selenium process finished.
I am trying to attach the Nuclide debugger to Expo local server (port 19001), but it is showing me the following error :
Adapter node: v8.10.0 x64
vscode-chrome-debug-core: 3.17.10
Starting debugger app worker.
******** Unhandled error in debug adapter - Unhandled promise rejection: Error: spawn react-native.cmd ENOENT
at _errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
Followed by:
Could not debug. Invalid Version: