Explain end-to-end testing life cycle with different models

  • Interview Candidate
  • 7
  • 6026

Showing Answers 1 - 7 of 7 Answers

nandababu

  • Dec 12th, 2006
 

End to End Testing is nothing but System Testing.The term system testing means Combination of Functionality testing and Non-Functionality Testing.

  Was this answer useful?  Yes

BTK

  • Jun 26th, 2007
 

End-to-End Testing will be done in two ways:
 a) E2E within the system or same application
 b) E2E with down/up stream application(s)

The above a) and b) will be considered based on the time and cost of the project
 
a) E2E within the system: This is nothing but all the possible scenarios that will be used in the application. This is part and parcel of system testing.

b) E2E with down/up stream applicaiton(s): This will be done before or after system testing is completed which depends up on time and cost of the project. This can be done in two ways:
        i) High level
       ii) Low level

    i) High level: Here we will only check that the records created in our applicaiton are visible in other down/up stream applicaiton(s), which is verified by the down/up stream application's test team. Validation of data is not done in this level.

   ii) Low level: Here we will check that the records created in our system are visible in other down/up stream application(s), verificaiton of data, validation of data, reflection of updates in base application which are done in down/up stream application(s), impact testing are done in this level.  

  Was this answer useful?  Yes

saravanan123

  • Jul 20th, 2009
 

End-to-end testing is the process of testing transactions or business level
products as they pass right through the computer systems. Thus this generally
ensures that all aspects of the business are supported by the systems under
test.

This ensures that the overall process flows as expected, that is that system
components integrate together correctly and that the right information is passed
between them.


The process may fail and there could be omissions in the process.
Dependencies may not have been identified and incorrect information could be
passed between system components and systems. The software may work, but the
overall process does not (for example, people order goods, but they are never
delivered).


  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions