playwright

While I do agree, then you don't have to run Selenium tests on your PC, but let it be done by e.g ci/cd Also depends how many pages do you want to test with Selenium - if you want to test e.g 5 pages, then it'll be fast enough I guess. There are a few tricks/configurations that make Selenium significantly faster - https://stackoverflow.com/a/57720610 A lot of is also on how do you write your "testing infrastructure" - maybe you could reuse engine/browser instance? execute tests parallelly? There's also alternative to Selenium by Microsoft: https://github.com/microsoft/playwright AFAIK it's way more reliable than Selenium (false errors) __________ Overall you can still start application inside tests with different startup, without Selenium and send http requests, so you'll have end-to-end tests done fast.

supposedly some of the key contributors are the same people who also built puppeteer and the objective seems to be taking it a step further to support ALL rendering engines [0] >We are the same team that originally built Puppeteer at Google but has since then moved on. Puppeteer proved that there is a lot of interest in the new generation of ever-green, capable, and reliable automation drivers. With Playwright, we'd like to take it one step further and offer the same functionality for all the popular rendering engines. We'd like to see Playwright vendor-neutral and shared governed. [0] https://github.com/microsoft/playwright/pull/711/files

If it's a website, I'd look into https://www.cypress.io or https://github.com/microsoft/playwright