[troglodynellc]

Playwright is a breath of fresh air next to selenium. And I maintain the perl selenium client and have written thousands of selenium tests!

So much so that I wrote what may? be the first third-party client for it: https://metacpan.org/pod/Playwright

Here's my writeup on why I like playwright versus selenium: https://troglodyne.net/posts/1617057517

[pydry]

That's a really good explanation. It's funny that they don't mention or allude to any of this in their page on why playwright: https://playwright.dev/docs/why-playwright/

[troglodynellc]

That doesn't really surprise me to be honest.

Most of this is invisible to end-users of selenium, as it's just a hammer they pick up; the struggles of the maintainers is not (nor should it be) something they have to worry about.

Nevertheless, they probably could get some hay mentioning that their API implements a significant amount more functionality versus every other cross-browser testing framework.

That said, they really don't have to, the work really stands by itself.

[Vinnl]

That is an excellent write-up, and assuages the main concern I was still having with Playwright (Playwright itself addressing the main concern I had with Puppeteer, which was its focus on a single browser). Thanks for sharing!