Current time: 11-19-2019, 06:37 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error running mobile test
02-10-2016, 06:07 AM
Post: #1
Error running mobile test
Mobile tests are failing. Below is the output could you take a look and perhaps point me in the right direction. Config: Physical window 7 machine running website, desktop wptdriver agent, url blast, and wpt_agent for a connected MotoE.

E Feb_09_14:44:52.552 C:\wpt\agent\js\src\wd_server.js:208 WebDriverServer.<anon
ymous> : Exception from "Run test": Error: spawn chrome ENOENT
E Feb_09_14:44:52.564 C:\wpt\agent\js\src\wd_server.js:1106 WebDriverServer.<ano
nymous> : App uncaught exception event: [{"code":"ENOENT","errno":"ENOENT","sysc
all":"spawn chrome","path":"chrome","spawnargs":["--disable-fre","--enable-bench
marking","--metrics-recording-only","-remote-debugging-port=1234","-remote-debug
ging-port=1234"],"webdriver_promise_error_":true}]
C Feb_09_14:44:52.565 C:\wpt\agent\js\src\wd_server.js:1482 WebDriverServer.onUn
caughtException_ : Uncaught exception: Error: spawn chrome ENOENT
at exports._errnoException (util.js:856:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:474:9)
at process._tickCallback (node.js:388:17)
==== async task ====
chrome --disable-fre --enable-benchmarking --metrics-recording-only '-remote-deb
ugging-port=1234' '-remote-debugging-port=1234'
at app.schedule (C:\wpt\agent\js\src\process_utils.js:392:20)
at Object.exports.scheduleSpawn (C:\wpt\agent\js\src\process_utils.js:364:14
)
at BrowserLocalChrome.BrowserBase.startChildProcess (C:\wpt\agent\js\src\bro
wser_base.js:59:24)
at BrowserLocalChrome.startBrowser (C:\wpt\agent\js\src\browser_local_chrome
.js:112:8)
at WebDriverServer.startChrome_ (C:\wpt\agent\js\src\wd_server.js:251:17)
at WebDriverServer.runPageLoad_ (C:\wpt\agent\js\src\wd_server.js:1028:10)
at WebDriverServer.<anonymous> (C:\wpt\agent\js\src\wd_server.js:679:12)
at webdriver.promise.ControlFlow.runInNewFrame_ (C:\wpt\agent\js\node_module
s\selenium-webdriver\lib\webdriver\promise.js:1438:20)
at webdriver.promise.ControlFlow.runEventLoop_ (C:\wpt\agent\js\node_modules
\selenium-webdriver\lib\webdriver\promise.js:1303:8)
==== async task ====
Run test
at app.schedule (C:\wpt\agent\js\src\process_utils.js:392:20)
at WebDriverServer.scheduleNoFault_ (C:\wpt\agent\js\src\wd_server.js:207:20
)
at WebDriverServer.runTest_ (C:\wpt\agent\js\src\wd_server.js:675:15)
at WebDriverServer.connect (C:\wpt\agent\js\src\wd_server.js:1132:8)
at WebDriverServer.<anonymous> (C:\wpt\agent\js\src\wd_server.js:107:12)
at emitTwo (events.js:100:13)
at process.emit (events.js:185:7)
at handleMessage (internal/child_process.js:689:10)
at Pipe.channel.onread (internal/child_process.js:440:11)
Find all posts by this user
Quote this message in a reply
02-11-2016, 02:00 AM
Post: #2
RE: Error running mobile test
What command line are you passing to the Node js agent to control the Moto E? It looks like it is trying to launch a desktop browser.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)