[zirror]

Yes, way more stable. At least cypress, I don't have much experience with playwright. We never had an issue regarding brittleness or stability. We do, however, get sometimes frustrated over certain API choices, like the way sessions and cookies are managed and how hard it is to keep a value throughout a test suite etc.

[lloydatkinson]

Quite literally every Selenium test I’ve had access to has been a total disaster. When your build pipelines fail 50/50 because of some bullshit Selenium timeout no one can reproduce that resolves itself the next run, it’s time to look at another tool. Not to mention that the Selenium port for .NET is a literal verbatim translation from Java and written by people clearly not versed in C#. The API and way the library works are nothing like how you’d expect a C# library to work.

For example class properties are not meant to do expensive work and yet they directly interface with the IPC to the browser. This means debugging in Visual Studio becomes impossible in any meaningful way. Hovering over a property while paused on a breakpoint will trigger some command in the browser that might throw an exception which causes an exception in the debugger.

Playwright, Cypress, Web Driver are simply what should be considered the defaults in 2022.

[mesadb]

100% agree but I still think there are still people using Selenium. I think we could help people navigate to Cypress or Playwright or no-code solutions