When to skip end-to-end testing
As an experienced Android developer and tech leader, I’ve learned a lot about the importance of testing. However, I’ve also learned that there are times when it’s simply not worth the effort to write end-to-end (E2E) tests.
E2E tests are designed to verify that a complete system works as expected. This means that they typically involve interacting with multiple components, such as the user interface, the backend, and even third-party services.
In some cases, writing E2E tests can be very challenging. For example, if you need to test a feature that requires user input, such as signing up for a service, you’ll need to find a way to simulate that input in your tests. This can be difficult and time-consuming.
In other cases, the cost of writing E2E tests may simply be too high. For example, if you need to test a feature that requires access to a third-party service, you may need to pay for that service.
So, when should you skip E2E testing? Here are a few tips:
- If the feature is relatively simple, you may be able to get away with unit or integration testing. These types of tests are typically easier to write and maintain than E2E tests.
- If the feature is unlikely to change, you may be able to get away with manual testing. This is a good option if you have the resources to dedicate to manual testing.
- If the cost of writing E2E tests is too high, you may need to find a workaround. For example, you could write a test that only verifies the initial state of the feature.
- Of course, there are also benefits to writing E2E tests. For example, they can help you to catch bugs that would otherwise go undetected. However, it’s important to weigh the benefits against the costs before deciding whether or not to write E2E tests.
Positive business perspective
There are several positive business perspectives of skipping E2E testing. First, it can save time and money. E2E tests can be time-consuming to write and maintain, and they can also be expensive to run. By skipping E2E testing, you can free up resources to focus on other areas of your business.
Second, skipping E2E testing can help you to ship products faster. E2E tests can add a significant amount of time to the development process. By skipping E2E testing, you can get your products to market sooner.
Third, skipping E2E testing can reduce the risk of overtesting. E2E tests can be very thorough, but they can also be overkill. By skipping E2E testing, you can focus on testing the most important aspects of your products.
Of course, there are also some risks associated with skipping E2E testing. For example, you may miss some bugs that would otherwise be caught by E2E tests. However, by following the tips above, you can minimize these risks.
Ultimately, the decision of whether or not to skip E2E testing is a judgment call. However, by carefully considering the pros and cons, you can make the best decision for your business.