Currently we do not have any automated end-to-end tests.
During development, we will describe which features we add to the requirements.md file in the docs of the respective app.
This will result in a list of features and requirements that we can test.
Initially, this testing will be done manually. Eventually, we will create automated tests for this.
To ensure the quality of our code, we write unit tests for our React components.
For the components in our libraries (/libs) we use Vitest with React Testing Library.
For the components in our applications (/apps) we use Jest with React Testing Library.
The reason for this difference is simply that Nx, our monorepo tool, automatically sets it up this way. We currently don’t have any reason to change it, seeing as the syntax for Jest and Vitest is largely the same. If this causes issues in the future, we might reconsider this choice.
We aim to have a unit test for all React components. A unit test should test functionality, not implementation details. In other words, it should test a component the same way a user would use it.
For that reason, we avoid using test ids (which is something a user can’t / won’t use), and instead find elements by their accessible name.
React Testing Library has nice documentation on how to find elements, where they prioritize the queries you can use.