What is System integration testing?
- System integration testing (SIT) tests the interactions between different systems and may be done aftersystem testing.
- It verifies the proper execution of software components and proper interfacing between components within the solution.
- The objective of SIT Testing is to validate that all software module dependencies arefunctionally correct and that data integrity is maintained between separate modules for the entire solution.
- As testing for dependencies between different components is a primary function of SIT Testing, this area is often most subject toRegression Testing.
Other popular articles:
- What is Big Bang integration testing?
- What is Component integration testing?
- What are Software Testing Levels?
- What is Integration testing? Examples, How To Do, Types/Approaches, Differences
- What is Component testing?
Reader Interactions
Comments
Chetansays
It’s a tricky question, that SIT should perform after Unit testing or System Testing. You need to understand the definition of Unit and System first.
If we are taking about testing a product which is integrating 5 different systems, then the individual systems which are already tested individually and operational, will be considered as individual units for this new Product, so considering this, First Unit testing is done (testing individual systems), after that System Integration Testing performed and at last the System Testing (product testing as whole) will be done. Hope you get the point.Lilysays
In ISTQB 2018 syllabus, it says “System integration testing may be done after system testing or in parallel with ongoing system test activities” in 2.2.2 Integration Testing.
mybrainssays
example – The starting point is you need to be clear what you define is a system. In this example I defined a system as a complete deployed product/application. SIT is often used in big organization were multiple products are connected together and testing is a workflow between these . Take for example a commercial bank. They may have a mainframe system, an online banking system a credit card processing system and so on. They need to test that all these systems can work together – An example test case may say they want to release a new feature that brand new users that register for the latest credit card will get no fees on their online banking. This workflow will require all systems to respond in an integrated way. The endpoints to the test case start at the new user registration and flow through. Hope this helps.
mybrainssays
example – The stating point is you need to be clear what you define is a . In this example I defined a as a complete deployed product/application. SIT is often used in big organization were multiple products are connected together and testing is a workflow between these . Take for example a commercial bank. They may have a mainframe , an online banking a credit card processing and so on. They need to test that all these systems can work together – An example test case may say they want to release a new feature that brand new users that register for the latest credit card will get no fees on their online banking. This workflow will require all systems to respond in an integrated way. The endpoints to the test case start at the new user registration and flow through. Hope this helps.
Ankitsays
For Example if an application has 8 modules. Testing the entire application with all 8 modules combined, we call it System testing and if application interacts with some other applications (External systems) to retrieve or send data, to test with other application and external system or any other module we call it Integration testing or system integration testing.
Upasanasays
I have read this every that SIT is performed after system testing. But it should be after Unit testing. How can we test system as a whole first then we will perform integration testing on it later. We always perform Unit testing first and then integration and then system.
For eg: Test of a system(Coffe Mug).
Unit Test first : Handle individually and mug without handle.
System Integration: After joining the handle we will test if it stable and reliable and all testing there.
System Testing: After both the process above we will test whole mug.This is What I think should be followed, then what is the exact reason to do system test before system integration testing. Why even this is mentioned in ISTQB docs too.
Renato Linssays
SIT is different than integration testing. The focus of this second is on the components integration while SIT the focus is to test integration between systems.
Anandsays
As mentioned here, SIT is done after System testing. But as per my opinion, it should be targeted prior to System testing. Once you are sure integration between components is working fine, then only you should take system testing.
To give example, if operation of your application is highly dependant on different values of database, then target to choose test cases from system testing (or write separate SIT test cases) so that you ensure all different functionalities related to integration works fine.
Then in the next phase of System testing you focus on wider coverage of testing.Bhabishsays
For example at system level we are working on 3 components which are inter dependent. We do the system testing for those 3 components. Afterwards when we integrate those 3 components into one module, we again do testing in order to check that module is working as per after integration of all 3 components. That means there is no functional dependency with respect to data or anything.
This is so called SIT.Yogesh Negisays
I am also waiting for example so that it could be clear what is SIT.
Nataly Portmansays
Can someone comment an example? Please.