angular-testing-library VS cypress-testing-library

A few months ago some colleagues told me about their smooth experience with Jest and Testing Library in a Vue application. Last week I gave it a shot. It took me a couple of hours to remove all Karma and Jasmine dependencies, and to properly configure this new testing platform. After that, I tried to refactor a small component by test driven development, again. This time, it was easier to render each component and its dependencies. However, there weren't enough enough examples and real use cases for testing the actual behavior of the components with ease (even with resources like this or this).

Angular Testing Library Repository Buenas prácticas con Angular Testing Library

One of the additional layers you can add to make sure you are building a good, accessible app, is to use “accessible queries” for elements you interact with in the tests. In other words, you find elements by text, labels, roles, aria-attributes, etc., rather than using the IDs or data-test attributes. This applies to all layers of testing. There is a very useful project called Testing Library, which provides you with UI-centric queries out of the box. It has a separate package for many different testing methods and libraries, including the Cypress one: Cypress Testing Library.

Is it a react app? Could be dom churn on the CI? In which case you might take a look at this: potential fix in the CTL.

From doing some research it seems like most people use Testing Library for unit / integration testing and Cypress for E2E testing, but from reading the documentation of both it seems like you can use them for the same thing. There is also even a Cypress Testing Library to make things even more confusing. So what do you do? Use Testing Library for unit / integration testing and Cypress for E2E? Use Testing Library for everything? Use Cypress for everything? I'm just really curious what people think about this (and it seems like I'm not the only one.