You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a issue report but I'm curious as when I run autotest:e2e command, I got the following (with error):
"Running "connect:testserver" (connect) task
Started connect web server on 127.0.0.1:9999.
Running "shell:selenium" (shell) task
Running "watch:protractor" (watch) task
Waiting...>> '.\selenium\start' is not recognized as an internal or external command,
operable program or batch file.
Warning: Done, with errors."
Why am I seeing that error only on initial run?
It is confusing as I thought there was a failure at first.
Anyway, even with the error and the screen looked like it hung, if I make changes to the app or the test files, I see browser being opened and tests run correctly.
My system is a Windows 7.
The text was updated successfully, but these errors were encountered:
edrex
linked a pull request
Jan 5, 2014
that will
close
this issue
Hello,
This is not a issue report but I'm curious as when I run autotest:e2e command, I got the following (with error):
"Running "connect:testserver" (connect) task
Started connect web server on 127.0.0.1:9999.
Running "shell:selenium" (shell) task
Running "watch:protractor" (watch) task
Waiting...>> '.\selenium\start' is not recognized as an internal or external command,
Why am I seeing that error only on initial run?
It is confusing as I thought there was a failure at first.
Anyway, even with the error and the screen looked like it hung, if I make changes to the app or the test files, I see browser being opened and tests run correctly.
My system is a Windows 7.
The text was updated successfully, but these errors were encountered: