Chapter 1.2: Testing strategies: Automated E2E testing 🤑🤑🤑
Automated E2E testing helps us test our entire application from end-to-end with minimal manual effort. But what are the pros and cons of this type of automated testing?
Automated testing is the gold standard when it comes to ensuring that our application actually does what we expect it to do. Automation saves us a lot of manual effort, and we only need to write automated tests once to run them as often as we want (almost) for free. Therefore, we should try to automate every test we want to run regularly. This way, less manual testing is needed, and we can use the freed-up resources to build new features or find bugs that automated tests can't find.
Since we use E2E tests to test our entire system from end-to-end, i.e., including the surrounding infrastructure, they provide us with a very high degree of certainty that we can identify a large number of potential errors at an early stage. The more our test system resembles the production system, the more confidence we can have that, in the event of a successful test run, errors that are supposed to be covered by our tests will not occur on our production system either.
I value your advice!
What is your approach when it comes to running E2E tests?
Let us know in the comments!
However, this does not mean that our system is entirely bug-free! Tests can only prove that there are bugs, not that there are no bugs. If we find a new bug, either through manual testing or because it is pointed out to us by our users, a new test should be added as part of the bug-fixing process to ensure that the bug does not occur again in the future.
Overall, automated E2E testing offers us a high level of security and confidence, but this has its price.
Keep reading with a 7-day free trial
Subscribe to Good Tests for Vue Applications to keep reading this post and get 7 days of free access to the full post archives.