dom-testing-library VS cypress-testing-library

I did some digging and it looks like testing-library/dom-testing-library recommended using jest-environment-jsdom-sixteen in its release notes for v7.0.0 because CRA was using an older version of Jest which provided an older version of jsdom that was missing support for things like MutationObservers and other modern web features. However, eventually CRA was updated to use the newer version of Jest, and this made using jest-environment-jsdom-sixteen unnecessary – and in this case actually harmful as it prevented me from using the new useFakeTimers('modern') functionality. Once I removed the --env=jsdom-sixteen line from the test script in package.json everything started working as I expected.

"xByRole" is the most "correct" one, but it is also really slow if you're rendering something complex. Just a heads up. See this github issue for more info.

https://github.com/testing-library/dom-testing-library/issues/820#issuecomment-726936225

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.