Description
events.js:174
throw er; // Unhandled 'error' event
C:\Projects\Mobile\AWT>npm run browser-test
appium-webdriverio-tests@1.0.0 browser-test C:\Projects\MobileAPK\AWT
wdio ./config/wdio.browser.config.js
<<< BROWSER TESTS STARTED >>>
events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn appium ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
at onErrorNT (internal/child_process.js:421:16)
at internalTickCallback (internal/process/next_tick.js:72:19)
at process._tickCallback (internal/process/next_tick.js:47:5)
at Function.Module.runMain (internal/modules/cjs/loader.js:777:11)
at executeUserCode (internal/bootstrap/node.js:342:17)
at startExecution (internal/bootstrap/node.js:276:5)
at startup (internal/bootstrap/node.js:227:5)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:252:12)
at onErrorNT (internal/child_process.js:421:16)
[... lines matching original stack trace ...]
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! appium-webdriverio-tests@1.0.0 browser-test: wdio ./config/wdio.browser.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the appium-webdriverio-tests@1.0.0 browser-test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.