On one side, it has never been easier to generate tests. You can ask AI to write Playwright code. You can record flows. You can use no-code tools. You can plug tests into CI and get a demo running pretty quickly.
On the other side, a lot of teams still end up in the same place they were five years ago: fragile tests, low adoption, weird CI failures, browser differences, and one poor person maintaining a framework nobody else wants to touch.
So instead of writing another generic “best practices” post, I wanted to collect the pieces I would personally read before choosing a test automation approach in 2026.
Small disclosure: I work on Endtest, so many of these links are from the Endtest blog. But I think the topics are useful even if you are comparing Selenium, Playwright, no-code tools, AI testing tools, or a homegrown framework.
Start with the basics, but don’t stay there too long
