Selenium Tests Failing Resulting in "The Samplestack environment may not be properly configured"

[sjordan1975]

After running "gulp once --browser=chrome", ultimately I get ...

[09:48:13] Starting 'selenium-start'...
[09:48:13] using local Selenium server
selenium standalone is up to date.
chromedriver is up to date.
[09:48:13] Finished 'selenium-start' after 190 ms
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://172.30.98.112:59418/wd/hub
.
.
.
12 scenarios (11 failed, 1 passed)
105 steps (11 failed, 81 skipped, 13 passed)
Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 11 test(s)
[launcher] overall: 11 failed spec(s)
[launcher] Process exited with error code 1
[09:48:32] shutting down 3000
[09:48:32] shutting down middle-tier
[09:48:32] shutting down selenium
[09:48:32] 'e2e' errored after 18 s
[09:48:32] Error: 1
at done (/marklogic-samplestack/shared/js/dev-tasks/tasks/e2e.js:144:19)
at ChildProcess. (/marklogic-samplestack/shared/js/dev-tasks/e2e/protractor.js:140:5)
at ChildProcess.emit (events.js:98:17)
at Process.ChildProcess._handle.onexit (child_process.js:820:12)

Error(s) occurred.
The Samplestack environment may not be properly configured.
[09:48:32] 'once' errored after 2.48 min
[09:48:32] Error: 1
at formatError (/Users/sjordan/.nvm/v0.10.41/lib/node_modules/gulp/bin/gulp.js:169:10)
at Gulp. (/Users/sjordan/.nvm/v0.10.41/lib/node_modules/gulp/bin/gulp.js:195:15)
at Gulp.emit (events.js:95:17)
at Gulp.Orchestrator._emitTaskDone (/marklogic-samplestack/node_modules/gulp/node_modules/orchestrator/index.js:264:8)
at /marklogic-samplestack/node_modules/gulp/node_modules/orchestrator/index.js:275:23
at finish (/marklogic-samplestack/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:21:8)
at cb (/marklogic-samplestack/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:29:3)
at ChildProcess.onDone (/marklogic-samplestack/shared/js/dev-tasks/tasks/once.js:38:20)
at ChildProcess.emit (events.js:117:20)
at Process.ChildProcess._handle.onexit (child_process.js:820:12)

OS: OSX 10.10.5
gulp: 3.9
npm: 3.6
node: 0.10.41
phantomjs: 1.9.19

[laurelnaiad]

Could you post whatever information was snipped in the '. . .' phase between "Selenium standalone server started" and the summary? It's hard to tell what might have gone wrong, as the actual test failure logs aren't posted. Thanks!

[sjordan1975]

@laurelnaiad Please see attached log
log.txt

[laurelnaiad]

It really shouldn't be necessary for the tests, but I wonder how big the browser window is when the e2e tests are launched.... the test seems to be complaining that another element is obscuring the button it's trying to click.

Note: if you're not overly worried about the e2e tests and would rather play with the app, you should be fine doing gulp watch -- even though the script is saying it might not be configured properly, the fact is that you already have it configured -- it's just failing a test.

[sjordan1975]

@laurelnaiad Thank you. Per your instructions, I seem to now have the app up and running. I'll report back if I run into any more issues.

[laurelnaiad]

Sure, no problem! I will leave this open as a bug pertaining to the failing test. Thanks for the feedback!