Automated testing is a crucial part of high-quality software development. There are several dos and don’ts and pros and cons with every level of automated testing.
If you are not familiar with the different levels of automation, you can go from testing a unit of code (ex. a class), to test the integration of these units (ex. multiple classes), to the whole system. Testing is all about the risks and picking the right compromises. Given this, you should attempt to have a fairly balanced test suite so you don’t end up with days of running automation and you can have a fast and reliable feedback loop.
In this post, I’ll be focusing on a testing framework that currently helps with testing the whole system from a web browser. These types of tests are usually called UI tests, end-to-end tests, or system tests. While system tests are great, as they exercise the system from a user’s perspective, there are a few issues with these.
In this post, let's learn how to write end to end automation using Cypress. I’ll be focusing on a testing framework that currently helps with testing the whole system from a web browser.