-
Notifications
You must be signed in to change notification settings - Fork 2.3k
E2E testing with PhantomJS #189
Comments
While the case has been made that PhantomJS isn't ideally a choice for E2E - I also would like to figure this out for testing completeness. According to this SO thread linked below, PhantomJS is pretty quick and could be used as a first round E2E smoke test. I suppose there is also the possibility there is an end user purpose for consuming an web app programmatically (or in an automated server side fashion) with PhantomJS. Being a bit new with these tools, I've been floundering the past 24 hours getting Phantom set up with Protractor/Selenium - it is not a trivial solution. I am pretty close to getting it to work, but for some reason my Protractor-Jasmine-PhantomJS tests are currently running without executing the I would list my notes on how I got this far in the process, but I don't want to clutter the thread with a half baked solution . If I can resolve this, I'll come back. In the mean time, am hoping someone with more experience has insights. I'm going to circle over to a few other threads where folks appear to have been gotten latest Phantom working and cross post this link to see if anyone can enlighten. |
Also @simax , I think this thread should only address Protractor. Any Karma related info/issues should be posted to that repository. FWIW, I didn't encounter any issues with Karma and PhantomJS following this documentation: http://karma-runner.github.io/0.10/config/browsers.html |
Once there's a process it seems like one of the MD docs should be updated with how to get PhantomJS running so the insights aren't hidden away in these forums. Better yet, it may be worth integrating directly into Protractor like Karma did - imho. |
I just added https://github.com/angular/protractor/blob/master/docs/browser-setup.md which details how to set up browser configuration. This would be the perfect place to outline how to use PhantomJS. Happy to take pull requests updating that documentation! |
- Add notes about PhantomJS setup - May require further documentation.. Contributes to angular#189
Sorry about all the commits. Still learning git. |
I have followed the steps laid out but I can't get protractor/selenium/phantomjs to work. I have installed phantomjs globally
in my tests I have
at present I start all test manually from command line, starting up phantomjs first phantomjs then selenium java -jar selenium-server-standalone-2.35.0.jar and finally the protractor tests start node_modules.bin\protractor.cmd E2EConf.js my stacktrace is 16:33:37.125 INFO - Executing: [new session: {browserName=phantomjs}] at URL: /session) Could you confirm that I have taken the right steps in getting this running or have I done something wrong. |
- Add notes about PhantomJS setup. - May require further documentation. Contributes to #189
@Hardcode37 Not sure if I'll be of much help, but I noticed that I only As an aside, I was still never able to get phantom to connect to my local Hope this helps more than it confuses! On Thu, Nov 7, 2013 at 10:52 AM, Hardcode37 notifications@github.comwrote:
|
@juliemr I have a Vm on my mac which has centOS installed. When i run my tests using phantomjs capabilities they are running fine. I have a separate centOS host which i access remotely on which i have installed protractor. But when i run my tests on the host remotely i get the following error: /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1542 Not sure why this is happening when the configuration is same on both the VM and the linux host. I will appreciate any insights on this. |
Hi folks, Closing this issue as the specific problem here was addressed - please open a new issue or ask on stack overflow if there are continuing problems. |
Can anyone list the steps required to get end to end testing set up with
karma/protractor
etc. My e2e tests run fine with chrome but I can't seem to find any good documentation on setup usingPhantomJs
.The text was updated successfully, but these errors were encountered: