How do you decide the scope and level of system integration testing vs end to end testing?

由人工智能和领英社区提供技术支持

System integration testing (SIT) and end to end testing (E2E) are two types of testing that aim to verify the functionality and performance of a software system as a whole. However, they differ in the scope and level of interaction between the system components and the external systems. In this article, you will learn how to decide the scope and level of SIT and E2E testing based on your project requirements, risks, and resources.

在这篇协作文章中查找专家回答

由社区从 3 条内容中精选。了解更多

1 What is SIT?

SIT is a testing process that focuses on verifying the integration of different modules or subsystems within a software system. It ensures that the data flow, communication, and functionality between the components are working as expected. SIT can be performed at different levels of granularity, such as component integration testing, subsystem integration testing, or system integration testing. SIT can use various techniques, such as top-down, bottom-up, or hybrid approaches, to test the integration of components.

添加您的观点

2 What is E2E?

E2E is a testing process that simulates the real-world scenarios and user interactions with the software system. It checks the end-to-end functionality and performance of the system across multiple layers, such as the user interface, the business logic, the data access, and the external systems. E2E can use various tools, such as automation frameworks, test scripts, or test data, to execute the test cases.

添加您的观点

Rene' Savage

Retired
举报内容
E2E testing is well defined above. This is the type of testing we needed to do whenever we had a huge change or a new system began to interface with us. Some of our day-to-day testing might include E2E testing of a process, not the system.

已翻译

赞

3 How to decide the scope of SIT and E2E?

The scope of SIT and E2E testing depends on the complexity, size, and architecture of the software system, as well as the quality objectives, risk factors, and stakeholder expectations. Generally, testing should cover the critical and high-risk features and functionalities of the system, the interfaces and interactions between the system components and external systems, the main user journeys and workflows of the system, and the non-functional requirements and performance criteria.

添加您的观点

Rich Jordan

Enterprise Solutions Architect at Curiosity Software
举报内容
Scope system integration testing (SIT) to validate seamless data and process orchestration between integrated components or services. Analyze key integration touchpoints from requirements, highlighting sinks and sources to be tested. Understand component functionality to drive test case design across linking activities. End to end (E2E) testing should focus on critical major user journeys. Walk through workflows to outline steps, taking note of systems engaged. Define the production-like test environment needed to mimic flows. Review risks, complex elements and quality objectives to guide test coverage & technical validation rigor. Well-defined scope targeting key integration touchpoints & limits of blast radius (need to do exhaustive e2e)

已翻译

赞

4 How to decide the level of SIT and E2E?

When determining the level of SIT and E2E testing, consider factors such as the availability and reliability of the system components and external systems, the cost and effort of setting up and maintaining the test environment and data, the feasibility and efficiency of automating and executing test cases, as well as the feedback loop for test results and defect resolution.

添加您的观点

Rene' Savage

Retired
举报内容
With a system that needs to test on a regular basis when new changes are completed and ready to be tested, we already had our test environment with test data. Our company also had test systems so that we could test as needed. Other systems did the same. Since we use inventory when testing shipping, our systems could get out of sync. But no problem. We could create inventory as well. Basically, SIT was only needed if we had to test between systems, it could be a simple update to one transaction. Or it could be a change that goes to multiple systems and one is a new system, which could mean E2E. But E2E can be broken down to a process as well.

已翻译

赞

5 How to balance SIT and E2E?

SIT and E2E testing should be planned and executed in a coordinated and iterative manner to ensure the quality and reliability of the software system. To balance SIT and E2E testing, it is recommended to follow the testing pyramid principle. This suggests that most testing should be done at the lower levels of the system, such as unit testing and component integration testing, which are faster, cheaper, and easier to automate and maintain. A moderate amount of testing should be done at the middle levels of the system, such as subsystem integration testing and system integration testing. Finally, a minimum amount of testing should be done at the higher levels of the system, such as end to end testing and user acceptance testing, which are the most complex, expensive, and hardest to automate and maintain.

添加您的观点

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Integration Testing

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you decide the scope and level of system integration testing vs end to end testing?

1

2

3

4

5

6

1 What is SIT?

2 What is E2E?

3 How to decide the scope of SIT and E2E?

4 How to decide the level of SIT and E2E?

5 How to balance SIT and E2E?

6 Here’s what else to consider

Integration Testing

给文章评分

感谢您的反馈

更多Integration Testing相关文章

更多相关阅读内容