Closed jewelsjacobs closed 10 years ago
Anyone with protractor experience that can help Julia?
On Mon, Jun 30, 2014 at 6:33 PM, Julia Jacobs notifications@github.com wrote:
Tried to get this to work with phantomjs and had no joy :(
Installed protractor globally add created a new task called spec-e2e-ci.coffee which just referenced a new config file called spec-e2e-ci.js
I replaced the
capabilities: { 'browserName': 'chrome' }
with
capabilities: { 'browserName': 'phantomjs' }
$ ➜ load-balancer-service git:(master) ✗ lineman grunt spec-e2e-ci Running "spec-e2e-ci" task Starting selenium standalone server... Selenium standalone server started at http://10.1.57.30:62627/wd/hub
Load Balancers Page 1) "before all" hook
0 passing (10s) 1 failing
1) Load Balancers Page "before all" hook: Error: Timed out waiting for page to load Wait timed out after 10049ms
I'm using mocha+chai btw which works fine with the regular spec-e2e / chrome driver setup so I don't think that's what's causing the problem.
Do you know a way to get this to work?
Any hints?
— Reply to this email directly or view it on GitHub https://github.com/linemanjs/lineman-angular-template/issues/50.
Hi @searls,
I actually decided to use xvfb with firefox and then the Xvfb Jenkins plugin.
I don't think phantomjs was the best solution for my setup . . .
Not sure if I should close this in case anyone wants it for a reference, though.
Go ahead and close until someone needs help
On Wed, Jul 2, 2014 at 2:59 PM, Julia Jacobs notifications@github.com wrote:
Hi @searls, I actually decided to use xvfb with firefox and then the Xvfb Jenkins plugin. I don't think phantomjs was the best solution for my setup . . .
Not sure if I should close this in case anyone wants it for a reference, though.
Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman-angular-template/issues/50#issuecomment-47820157
Tried to get this to work with phantomjs and had no joy :(
Installed protractor globally add created a new task called spec-e2e-ci.coffee which just referenced a new config file called spec-e2e-ci.js
I replaced the
with
I'm using mocha+chai btw which works fine with the regular spec-e2e / chrome driver setup so I don't think that's what's causing the problem.
Do you know a way to get this to work?
Any hints?