Correcting Wrong ‘Playwright’s Advantage over Selenium” Part 7: “Playwright supports a range of Testing Types, e.g. API Testing”

Don’t Compare Apples to Oranges. Focus on real E2E UI Testing, which Playwright is still far behind raw Selenium.

Continue to correct the 7th wrong claim in this YouTube video, “Playwright vs Selenium: What Advantages Make Playwright the Winner in Automation Testing Battle 🏆”.

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.” 👎🏽 (coming)
• “Playwright ARIA locator support” 👎🏽
• “Playwright has frequent releases” 👎🏽
• Wrap-Up (coming)