3 ms·

I once wanted to do automated testing with it. But because PhantomJS used an old webkit version, I couldn't :( But that's one use case where I would love to us

by pothibo 12y ago

I once wanted to do automated testing with it. But because PhantomJS used an old webkit version, I couldn't :( But that's one use case where I would love to use phantomJS or any other headless engine to test the frontend. I'm aware that for headless testing to work, there should be a headless browser of every major vendor. Maybe it's an utopia.

serve_yay 12y ago
Yes, my team ran directly into the old webkit version issue as well. Does this 2.0 still use an old WebKit? Having trouble finding out... Edit: it appears to be WebKit 538.1, from May 2014. But this is based on a readme which is pretty old, so it could be outdated info
- simlevesque 12y ago
  I have solved this problem by using SlimerJS as an alternative.
  - serve_yay 12y ago
    Yeah, unfortunately we can't install that one on our build box, I believe because it needs X11. (As the page says it is not "totally headless")
    - simlevesque 12y ago
      You are mistaken. You can install SlimerJS on a box without X11. You must install Xvfb use it like this : xvfb-run slimerjs script.js If you use casperjs you can modify the executable (it's python) and change "'default_exec' : 'slimerjs'" into "'default_exec' : 'xvfb-run slimerjs'"
- pothibo 12y ago
  It uses a new version of Webkit(That includes DOM Mutation Events IIRC). But I believe that they always ship with their own version of webkit, which will always be behind. For PhantomJS 2.0, I think they ship with a version of webkit that is > 6 months old.
  - warfangle 12y ago
    They don't ship with their own version of webkit; they use qtwebkit (or at least used to?).
jamespitts 12y ago
I've been using jquerygo (which runs on phantomjs) to do automated UI testing. The familiar jquery selectors are convenient! Being able to use websockets in my automated testing has been something of a holy grail, so jquerygo and phantomjs have been hugely helpful. https://github.com/travist/jquery.go.js https://github.com/travist/jquery.go.js

by pothibo 12y ago

serve_yay 12y ago

Yes, my team ran directly into the old webkit version issue as well. Does this 2.0 still use an old WebKit? Having trouble finding out... Edit: it appears to be WebKit 538.1, from May 2014. But this is based on a readme which is pretty old, so it could be outdated info

simlevesque 12y ago
I have solved this problem by using SlimerJS as an alternative.
- serve_yay 12y ago
  Yeah, unfortunately we can't install that one on our build box, I believe because it needs X11. (As the page says it is not "totally headless")
  - simlevesque 12y ago
    You are mistaken. You can install SlimerJS on a box without X11. You must install Xvfb use it like this : xvfb-run slimerjs script.js If you use casperjs you can modify the executable (it's python) and change "'default_exec' : 'slimerjs'" into "'default_exec' : 'xvfb-run slimerjs'"
pothibo 12y ago
It uses a new version of Webkit(That includes DOM Mutation Events IIRC). But I believe that they always ship with their own version of webkit, which will always be behind. For PhantomJS 2.0, I think they ship with a version of webkit that is > 6 months old.
- warfangle 12y ago
  They don't ship with their own version of webkit; they use qtwebkit (or at least used to?).

jamespitts 12y ago

I've been using jquerygo (which runs on phantomjs) to do automated UI testing. The familiar jquery selectors are convenient! Being able to use websockets in my automated testing has been something of a holy grail, so jquerygo and phantomjs have been hugely helpful. https://github.com/travist/jquery.go.js https://github.com/travist/jquery.go.js