3 ms·
I really wish we had a good set of scriptable browser engines (i.e. everything but the graphics part) for all browsers. That would make testing so much easier.
by VeejayRampay 10y ago
I really wish we had a good set of scriptable browser engines (i.e. everything but the graphics part) for all browsers. That would make testing so much easier.
Even simple tasks like taking a screenshot of a given web page involves PhantomJS, which seems really heavy-handed.
Thanks for compiling this list but the issue I'm having with this is the lack of a rating system based on usage, Github stars, downloads, repo activity, project creation, corporate support, etc. to get a measure of how reliable those tools are.
- mping 10y agoYeah, some are quite old and discontinued. I currently use Nightmare which is electron based and has a nice api. Tried a couple others but every time something went wrong.
- icebraining 10y agoThe problem is that to take a screenshot of how the page actually looks, you need almost everything from the browser. Rendering of HTML/CSS/images/videos, Javascript execution, networking, cookies... you end up with 90% of the browser, and then removing the last 10% is not worth it.
- nattaylor 10y agoIf all you want to do is take a screenshot, I've had success with http://wkhtmltopdf.org/ http://wkhtmltopdf.org/ (which also outputs to image formats.) You can't script it though.
- bzbarsky 10y agoThe problem is that the "graphics part" is often the part that knows how to deal with fonts, which you sort of need for layout.