Introducing Playwright for E2E tests

In E2E tests, we need to ensure that our system is fully behaving as expected, including the interaction with external services, such as the web API.

Even though unit testing is more crucial than E2E testing, a great testing strategy includes all different types of tests, including unit tests, integration tests, E2E tests, and performance tests. The reason why automated E2E tests are less important than unit tests is that all the components have to be available and running. In our case, every time you want to run E2E tests, the API has to be up and running, and a sandbox environment has to be available, otherwise the tests will keep adding, editing, or deleting data if the API doesn’t support test data. E2E tests are also slower to run, so running them all the time, as we can with unit tests, is not preferable.

E2E tests complement rather than replace unit tests for the product’s overall testing. E2E testing is not meant to replace...