Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
blog.checklyhq.com
Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
1–10 of 31 posts
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#2I knew before even looking at these that Playwright and Puppeteer would be the best performers. However, they didn't really go into a lot of details about system configuration and browsers which can also have a significant impact on performance.
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#3No cypress?
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#4I knew before even looking at these that Playwright and Puppeteer would be the best performers. However, they didn't really go into a lot of details about system configuration and browsers which can also have a significant impact on performance.
Author here - I'd be keen to go into further detail in a follow-up article if people are interested. Out of curiosity, what details would be most interesting for you about system and browser config?
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#5No cypress?
In the near future.
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#6While interesting, performance is a tiny concern here. Most browser automation is going to have a lot of implicit and explicit waits that dwarf the differences in performance between libraries. Moreover, someone may choose Puppeteer over Selenium for functional differences (for example, Selenium is easier to catch and block)
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#7Interesting.. I've chatted with Tim and learned a lot of people run Puppeteer on Lambda.. there is an easier way (spoiler - I work on the open source project OpenFaaS) - https://www.openfaas.com/blog/puppeteer-scraping/
Hope it's of some use to folks who may be struggling to compile lambda-chrome or with local testing.
I used Selenium a lot in a past life, so this post is interesting to see, but the UX and maintenance cost is also going to need to be factored in with bigger suites of tests.
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#8Interesting.. I've chatted with Tim and learned a lot of people run Puppeteer on Lambda.. there is an easier way (spoiler - I work on the open source project OpenFaaS) - https://www.openfaas.com/blog/puppeteer-scraping/ Hope it's of some use to folks who may be struggling to compile lambda-chrome or with local testing. I used Selenium a lot in a past life, so this post is interesting to see, but the UX and maintenanc…
The combination of headless browsers and any form of FaaS / Lambda / serverless solution is immensely powerful. There are all kinds of businesses popping up around this tech stack, of which my business is one.
OpenFaaS is a great alternative that we will surely test drive.
AWS now supporting containers on Lambda will hopefully make shipping browser binaries to Lambda also easier.
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#9It would be interesting to see a raw selenium comparison -- WDIO is slower with both backends, it could be that selenium and puppeteer are both about as fast, and the performance difference is mostly about higher-level framework.
Re: Benchmark: Puppeteer vs. Selenium vs. Playwright vs. WebDriverIO
#10While interesting, performance is a tiny concern here. Most browser automation is going to have a lot of implicit and explicit waits that dwarf the differences in performance between libraries. Moreover, someone may choose Puppeteer over Selenium for functional differences (for example, Selenium is easier to catch and block)
It is indeed hard to have an all-encompassing comparison that will take everything into account. Unfortunately, to have precise answers in feasible time you have to narrow the scope. Here we looked at one parameter of a complex equation.