Correcting Wrong “Playwright’s Advantage over Selenium” Part 1: “Playwright is Modern and Faster than Selenium”

New ≠ Modern ≠ Better. Faster? I haven’t seen a truly successful Playwright implementation with a large suite yet.

🎖The article was selected by Medium Curators for a Boost (“boost the best ideas and best information on Medium”), also one of my personal favorites.

Recently, I watched a YouTube video, “Playwright vs Selenium: What Advantages Make Playwright the Winner in Automation Testing Battle 🏆”.
Each of the presenter’s purported “Playwright Advantages” is either wrong or irrelevant in the context of real web test automation. I will elaborate on each of these points in this article series:

• “Playwright is Modern and Faster than Selenium” 😒
• “Playwright has Parallel Execution Support” 👎🏽
• “Playwright has Native Auto-Waiting Mechanism” 👎🏽
• “Playwright has a native test runner” 👎🏽
• “Playwright has native HTML Reporters” 👎🏽
• “Playwright Features Can be Configured in one Configuration” 👎🏽
• “Playwright supports a range of Testing Types, e.g. API Testing, Component Testing, …” 👎🏽
• “Playwright UI Mode, CodeGen, Debugging support.” 👎🏽
• “Playwright ARIA locator support” 👎🏽
• “Playwright has frequent releases” 👎🏽
• Wrap Up

How could this youtuber got it all wrong? Yes, it is very possible, because real automated engineers extremely rare. (Patrick Copeland, Google Senior Engineering Director, referred them as “Gold”)

Speaking of being off the mark totally, China International Capital Corporation made 10 predictions for the Chinese economy in 2023, and they all turned out to be incorrect!, that’s really hard, still, some ‘financial experts’ managed to accomplish that.

Table of Contents:
· My Objectiveness on Playwright
∘ 1. I do know a bit about Playwright
∘ 2. I added Playwright support in my testing IDE (TestWise) and award-winning CT server (BuildWise)
∘ 3…