cypress-testing-library VS cypress-a11y-testing

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.

In order to make it easier for you to follow, I’ve created a simple app that allows the user to submit a dummy form. You can find the repository here. Don’t worry, the data you submit in the app is not sent anywhere, so you can play around with it as much as you want.