What is the difference between system integration testing and end-to-end testing? With examples pls
- 1 Answers
- 4792 Views
- I also Faced
- E-Mail Answers
Answer Posted / ajit singh
System Integration testing is to ensure that software modules functionally correct after integration.
Example
So let's say you're developing a system A (e.g., online shop) that interacts with external (i.e., not under your control) system B (e.g., PayPal).
Testing whole system A you may verify whether it does what is was requested to, e.g., you are able to select and order a product (system A tests). You may also focus on integration problems here, e.g., because system A integrates backend with frontend (UI). For instance, how frontend behaves when backend is down or backend response is delayed?
Testing A integrated with B you may focus on different problems. You may verify whether after ordering a product money were transferred from your PayPal account to shop account (functionality). This is system C tests. You may also check what will happen when your online shop does not pass (optional) description in payment request to PayPal (more about integration). I would call this system C integration tests.
| Is This Answer Correct ? | 1 Yes | 1 No |
Post New Answer View All Answers
1) What r the properties, Advantages & Disadvantages of each types of action? 2)When I can use this?
Can anyone please tell me how to export the requirements from QC 9.2 to excel file.
What are the benefits of automated testing?
What is branch testing?
Can Parrto Principle be used in Quality Assurance and testing?
What is a test strategy and what does it include?
If there are more number of production defects, how will you tackle the team as a lead
How to design test cases?
what for cmmi and iso(what are they) are used and how we can use them in our testing and whole work related to sqa.Do it has any kind of format if it has kindly tell me from whr i will get it kindly give detalied answer?
what are the feature of our test group?
What are the dimensions of the risks?
What do you know about data-driven testing?
What if the software is so buggy it ca not really be tested at all?
Diffrence b/w compiled module and shared repository?
What is specification-driven testing?
