Skip to main content

What is End-to-end Testing with Example

End to End Testing is the approach in which tester/developer always validate whether the flow of application/software from the starting point to the end point is working perfectly or not.

End to End Testing Example - Real

For Example we are testing the web page of application than the start point will be logging in to web page and the end point will be logout of the web page means logout from the application/software.

So in this example of End to End Testing, tester/developer check whether the flow of application from starting to end point is working fine or not.

So in the above example when we login to the web page than tester/developer check that after login flow is properly working or not like they check after login we get into home page or not, they also check after login we are able to do some work or not, and finally they check after doing some little bit work we are able to logout from the application or not. So this is the End to End testing of web page performed by Developer/Tester, in which they check the complete flow of application from starting to end point.

Another Example of End to End Testing

Let’s take another example of this testing which is given below:
Suppose you are logging in to Gmail than End to End Testing is that after login you get into inbox or not, you are able to open and compose a mail or not, you are able to forward the mail or not, then finally you are able to logout from the Gmail or not. So this is the End to End Testing of Gmail in which tester check the flow of Gmail from starting to end point means from logging to logout point.

Conclusion

At end we conclude that End to End Testing is considered as the part of System Testing, and this testing is always conducted (carried out) to validate the flow of data between different modules. And you may also note that this testing is obviously conducted before closing the testing.

Comments

  1. Can we consider End to End testing as smoke testing techniques?

    ReplyDelete
    Replies
    1. No ,Smoke testing is just an initial testing where we test only basic and critical features of an application whereas in End to End testing we check each step from start to end point without skip.

      Delete
  2. first we perform system testing or end to end testing ? after ST & ETE is client perform UAT ?

    ReplyDelete
  3. keep writing informative article like this


    Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...