karma-ng-scenario icon indicating copy to clipboard operation
karma-ng-scenario copied to clipboard

Angular Scenario (run w Karma) mystery! … browser().navigateTo(…) never arrives

Open outrightmental opened this issue 10 years ago • 0 comments

I'm terrifically stumped here! Thanks so much for supporting this (now deprecated) library and THANKS INFINITE for any help solving this head-wall-banger.

I posted the issue here: http://stackoverflow.com/questions/22740818/angular-scenario-run-w-karma-mystery-browser-navigateto-never-arri but crickets so far.

Pasted below

Karma begins running e2e suite OK:

...
Running "karma:e2e" (karma) task
INFO [karma]: Karma v0.10.10 server started at http://localhost:8080/_karma_/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 33.0.1750 (Linux)]: Connected on socket XNRarLLpGwIi3U6mgiaw
GET / 200 345ms - 4.79kb

Now, notice that last line, the GET that goes out 200 OK is my grunt-launched express server doings its job fine.

At this point, I can see in my browser that the page has loaded successfully (Angular app IS running properly in the iframe)

describe: Front Page
  has expected sections
    browser navigate to '/'

BUT.. everything just hangs after that first navigateTo(). No errors. The test runner never recognizes that it has "arrived" at the target URL, ergo it never triggers anythings else.

outrightmental avatar Mar 30 '14 21:03 outrightmental