Quality Testing

Quality is delighting customers

Difference between System Testing and System Integration testing.......

HI all..

What is the difference between System Testing & System Integration Testing? Are the both same thing or just different?

Thanks in advance!!!!

Views: 28039

Reply to This

Replies to This Discussion

Systems Integration
System integration enables communication between many disparate systems and their processes. Integration is business development, including not only the core IT-systems of an organization but also its knowledge workers, customers and suppliers. When we connect different systems and applications you get faster communication with a higher security in your internal and external processes. Flexible organizations, where cooperation and optimization for existing or new business areas are in focus, have a already created and implemented software integration.

System Integration Testing (SIT), in the context of software systems and software engineering, is a testing process that exercises a software system's coexistence with others. System integration testing takes multiple integrated systems that have passed system testing as input and tests their required interactions. Following this process, the deliverable systems are passed on to acceptance testing.
Systems integration testing (SIT) is a testing phase that may occur after unit testing and prior to user acceptance testing (UAT). Many organizations do not have a SIT phase and the first test of UAT may include the first integrated test of all software components.

Integration testing

Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.

System Testing
System testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limiting type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.
System testing is actually done to the entire system against the Functional Requirement Specification(s) (FRS) and/or the System Requirement Specification (SRS). Moreover, the system testing is an investigatory testing phase, where the focus is to have almost a destructive attitude and test not only the design, but also the behaviour and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).
"System testing" is a high level testing, and "integration testing" is a lower level testing.

Integration testing is completed first, not the system testing.

In other words, upon completion of integration testing, system testing is started, and not vice versa.

For integration testing, test cases are developed with the express purpose of exercising the interfaces between the components.

For system testing, the complete system is configured in a controlled environment,

and test cases are developed to simulate real life scenarios that occur in a simulated real life test environment.

The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements.

The purpose of system testing is to validate an application's accuracy and completeness in performing the functions as designed,

and to test all functions of the system that are required in real life.

System Testing : Testing the system as a whole (both functionally and non functionally)


SIT: Testing the system with another system (It may be third party system or other system)



Ajay Pardhi

Hi Ajay,

This is shan. Hope u doing well.

Can u say about this diff between SIT and system testing with some example, if u dont mind?

And Can i get ur contact number ?


Thank you in advance 

It depends on who you are talking to as there is no real definition.

It was explained to me like that:

System Integration Testing is testing after combining two or more parts, e.g. 2 modules that should work together in the future, like a GUI and a DB or logic something. So you test integrity of modules with each other or in a bigger system (can also be a new feature that you test after being added into the system to know if it's still working like in unit test).


System Testing is also called Process Testing and describes the Test of the whole System, e.g. putting all testet modules together. This could be at a webshop: website-frontend + logic + db + ordering-api. Testing would include if the order done in the frontend (on the website) is correctly passed through all stages to the ordering-api (so you test if fedex will deliver really the blue shirt you ordered, not the default red one or something).


As i said this is just what i was told, but i think it's good ;) I hope my english wasn't to hard to read.





Thank you so much for all your replies :-D


TTWT Magazine





© 2018   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service