Web Automation: Don't Use Selenium, Use Playwright

• star-history

  18 3,633 7.7 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

  12 8,571 7.1 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

• Klotho

  klo.dev

  sponsored

  AWS Cloud-aware infrastructure-from-code toolbox [NEW]. Build cloud backends with Infrastructure-from-Code (IfC), a revolutionary technique for generating and updating cloud infrastructure. Try IfC with AWS and Klotho now (Now open-source)

  

• docker-headless-shell

  1 375 5.5 Shell

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

  

• Playwright

  161 47,154 10.0 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