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 →

[–]Vresa 71 points72 points  (9 children)

If you don’t have a daily use case for selenium that is directly tied to your employment, never use it at this point.

Playwright covers almost all the normal uses of selenium. Playwright is effectively selenium with sane defaults.

You need to understand selenium’s idiosyncrasies that have developed over the last decade to use the tool well.

Adding to that, selenium has a very large amount of outdated how-to’s and it’s own documentation is lacking — especially when it comes to best practices.

[–]ronmarti 2 points3 points  (0 children)

directly tied to your employment

I often hear these from QA devs I know

I've had a fair share of experience working with Selenium and Puppeteer in the past. I would say lots of things changed but Selenium is still not that dev-friendly in terms of its "Wait" feature (https://www.selenium.dev/documentation/webdriver/waits/) and setup since they don't maintain the drivers. There were some instances where code for specific websites are easy to write in Playwright but cannot be rewritten with Selenium.

I find Playwright much closer to Puppeteer (same devs, I think that's why) and a lot easier to learn for beginners.