Thank you for your kind words! :)
Lot's of things to say here but at least as a low-level comparison, I would refer you to a recent video youtube.com/watch?v=emWHeODwcQY
On a higher level Puppeteer is a library (the core if you may) of a web automation program that could evolve in a framework,
while Cypress is a full featured out of the box framework (with high customization capacity). At least in my eyes
I like the library concept. Cypress while lighter than Selenium, is heavy with Electron, in my opinion. I love the ease of use of Cypress, but I don't like the JQuery architecture. This is why this article was interesting to me. I looked at Puppeteer early on an didn't see the value over Selenium at the time. However, I'm thinking now that it's a Cypress killer due to it's library like way of doing things.
One last point, the Google chrome team uses Puppeteer to validate Chrome releases!
BTW Selenium just release a major version with lots of changes. It'll be interesting to see if Cypress and Puppeteer have set the standards. If they don't put in things like intercepting outbound and inbound http requests they aren't thinking right.
I am gonna cover the new version of Selenium in another post soon and also try to address why some "features" that we have in Puppeteer might be hard to get in Selenium with the current architecture.
Since you are interested in the library-style of tools, I would suggest you also take a look at a similar article introducing Playwright
Thank you for your kind words! :)
Lot's of things to say here but at least as a low-level comparison, I would refer you to a recent video youtube.com/watch?v=emWHeODwcQY
On a higher level Puppeteer is a library (the core if you may) of a web automation program that could evolve in a framework,
while Cypress is a full featured out of the box framework (with high customization capacity). At least in my eyes
I like the library concept. Cypress while lighter than Selenium, is heavy with Electron, in my opinion. I love the ease of use of Cypress, but I don't like the JQuery architecture. This is why this article was interesting to me. I looked at Puppeteer early on an didn't see the value over Selenium at the time. However, I'm thinking now that it's a Cypress killer due to it's library like way of doing things.
One last point, the Google chrome team uses Puppeteer to validate Chrome releases!
BTW Selenium just release a major version with lots of changes. It'll be interesting to see if Cypress and Puppeteer have set the standards. If they don't put in things like intercepting outbound and inbound http requests they aren't thinking right.
Thanks for sharing your thoughts!
I am gonna cover the new version of Selenium in another post soon and also try to address why some "features" that we have in Puppeteer might be hard to get in Selenium with the current architecture.
Since you are interested in the library-style of tools, I would suggest you also take a look at a similar article introducing Playwright
thehomeofwebautomation.com/getting...
Also I hope you find some more interesting stuff there!
Yes I saw PlayWright earlier this week. Wow, things are moving fast for sure....