End-to-end testing
End-to-end Testing (E2E) is type of software testing used to validate different integrated components of an application by testing the flow from start to end. It also tests the behavior of the application from start to end and check the whole system behavior according to the user requirements. End to End Testing tests the integrity of the integrated components as well as the integrity of the whole system. This is the reason it is called as end-to-end testing. End-to-end testing helps to ensure that the application will behave according to the requirements in development as well as in production or real-world scenarios.
Details
End to end testing is normally done after system testing. As we see end to end testing is all about the flow of the system, so it is done after the system is build and test. End testing verify and test the flow of the system with in the system as well as with the external systems.So it is preferred to do it after system testing.
End-to-end testing is similar to the system testing in that it tests the whole system, but in end-to-end testing it is actually the flow of the whole system according to the end-user scenario. End-to-end testing usually tests after system testing has completed and uses the actual environment data and test that data on production, So that the problems of the end user can be resolved and fix.
| End-to-end testing | System testing | |
|---|---|---|
| Testing | Flow of activities are tested | System as a whole is tested |
| Validation | Validating the data flow or process | Validating the system requirements |
| Dependency | Usually tested after system testing | Usually tested after integration testing |
| Preferred | Manual testing is preferred | Both manual and automation can be preferred |
| Requirements | Back-end and all the interfaces will be considered | Both Functional and non-functional requirements will be considered |
See also
References
- Rob Smit (2009). End to end Testing with TMap Next ISBN 9072194969