I have had nothing but headaches with phantomjs as the browser. Because of these issues I was thinking of alternative solutions like chrome with xcfb service on top. What are the best practices, or what ways have you worked around these.
Phantomjs is constantly giving me issues where either the Chrome and Firefox. As well it seems it has a random chance of crashing in ProtractorJs. There are other issues, and from what I can tell the bugs are in Phantomjs, but a lot of the bugs are being left over for a long time (relative to PhantomJS's history) . PhantomJs is still has issues with working in windows, luckily for me I don't have to use it. To me, it looks like that they are just going to release a phantomjs 2.0 in the near future, so should I even bother getting the bugs working. I see the e2e setups for Angular and the seed project and think that maybe this is the best solution. To make it work headless would require me to get a xvfb service running on the Linux build machine (And chromium at that point, maybe jump to firefox). I haven't done it yet and was wondering if it could solve my issues or just hold me off for the new release of phantomjs. Eventually maybe even going to a selenium farm, making or using someone like saucelabs, might be a solution. Was wondering what is considered the best practice for headless testing of e2e testing. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
