Web Automation: Don't Use Selenium, Use Playwright

• star-history

  36 5,809 8.9 TypeScript

  The missing star history graph of GitHub repos - https://star-history.com

  

For those of you who are as confused as I am about Playwright's growth over Selenium: https://star-history.com/#microsoft/playwright&SeleniumHQ/se...

My company uses Selenium for some of our projects, but I evaluated the browser automation space some time ago and found that it was the best-in-class solution at that time.

It looks like things have since changed.

• chromedp

  27 10,341 5.5 Go

  A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol.

  

Thanks. I've found Chromedp [0] to be a good Selenium replacement when programming in Go. Used in conjunction with HeadlessShell [1] you can deploy a Go app into a container and do the testing all within the same container with low overhead.

[0] https://github.com/chromedp/chromedp

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• docker-headless-shell

  1 432 0.0 Shell

  Minimal container for Chrome's headless shell, useful for automating / driving the web

  

• Playwright

  379 61,568 9.9 TypeScript

  Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

  

Using TLS client certificates automatically is still not possible in Playwright [1]. That's our main reason why we keep using Selenium (with pytest-selenium) and Selenium Grid [2].

[1] https://github.com/microsoft/playwright/issues/1799

Suggest a related project