Tips to integrate E2E testing into your existing test strategy
We have been talking about E2E testing in our previous articles, especially focusing on how to select right candidates for E2E testing and the major points you need to pay attention when initiating your E2E testing journey.
Here I have linked the previous 02 articles, since you are interested in E2E testing.
Have you defined the end-to-end test selection process in your project?
Tip: — Your application bugs reveal you a great story, where you need to pay attention, where the brittle code is.
05 secrets to adopt a successful E2E testing process.
This is one of the critical topics every testing team focus in their testing journey. Depending on the culture of the…
In this article, we are going to discuss on how to integrate E2E testing into an existing test strategy you have been following. At last, I promise to address one of the pitfalls most organisations face in their E2E testing journey.
Ask the question “Why do we really need E2E testing? and What problem are we going to solve with E2E testing?”
Let me share you an example. There is one famous strategy adopted in the industry where back-end is tested separately and front-end is tested separately with mocks and stubs. They meet each other only in the production. In this strategy, never a complete E2E is carried out. However, separate E2E tests may have been executed in each end. Of course this is a relative factor. My point is your prospective and definition on E2E should be according to your real requirement, not the generic definition of E2E.
If you are confident about the strategy you follow without E2E tests, you don’t need to implement another layer to make your life difficult. Most importantly don’t implement it for the sake of satisfying your higher management.
One fair reason to incorporate E2E testing could be due to identifying defects in production that were not captured by the existing low-level tests. Don’t hesitate to cross check if you have adequate low-level tests to cover the…