Cypress has become the preferred way of doing UI testing of Angular apps by many Angular experts.
It offers great improvements over Selenium based testing tools by making the testing experience more like a real user using the built-in retry mechanism of assertions and commands (eg. click on the element), a user-friendly GUI which makes it easy to trace what is going on in the tests.
But used wrongly, you will still face some of the classic end-to-end/UI test problems such as flakiness and slow test execution.
This post is extending upon the Cypress best practices combined with my experience from helping companies with Cypress testing.
Read more here.
Top comments (0)