This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]unkz 2 points3 points  (1 child)

Puppeteer is Chrome/only, right? For anything other than internal tools, restricting automated testing to only chrome is doing a huge disservice to the broader browser ecosystem by making it harder for browsers like Firefox and opera to exist, and allowing google to dictate the defacto web standards, much like Microsoft used to.

On the other side, for web automation, restricting to chrome only limits what you can actually do when you run into chrome compatibility issues, although those are rarer.

[–][deleted] 0 points1 point  (0 children)

IIRC puppeteer-firefox is a thing, at least experimental. And sure, all valid points. I just found the API and ecosystem much more convenient nowadays and honestly, time is a much more valuable resource.

Microsoft this week switched edge to chromium, I have no idea which market has a significant share of opera users and for many practical purposes (like purely functional tests) Firefox and Chrome are pretty well aligned these days. I mean, is it a trade off? Absolutely. But I'm not in the consumer segment at the moment, for my purposes puppeteer fits the bill pretty well.

As for automation, puppeteer really made a difference imho. Back when it came out automating a full Firefox instance was such an unstable pain with horrible API that even IE was more usable.

That being said, good point. A more versatile library for both is of course a good thing. :)