We're focused on code-based tests, which is a lot more flexible in terms of things they can test, and scales better with the complexity of your application and testing needs. (Can have test code that sets up mock data, shortcut parts of your application to speed up tests, work with dynamic data, and be updated alongside your product changes so your tests never break).
We've found that with the advancements in DX for e2e testing libraries today, most developers find it quicker to just write tests themselves in code, rather than having it done in a 3rd-party UI tool. This also gives the bonus that developers are aligned with delivering high quality, well-tested code during their development cycle, as opposed to encouraging a "throw-it-over-the-wall" culture of having someone else test it for them after broken code has landed into the main branch.
Last point, we're not a full testing framework ourselves - we're currently compatible with Cypress, a widely popular e2e testing library, but are definitely keeping an eye on other frameworks such as Playwright as well :)