System Integration Testing (SIT):
For better understanding of what is SIT first, we must understand what is System integration? so basically as the name itself suggest system integration refers as a set of phases where various components are incorporated in a single unit, and these units go for integration testing, the group of interaction between component is referred as integration and testing these interaction and modules interaction is known as integration testing.
From some other point of view, the SIT (system integration testing) is considered as the combination of integration testing and system testing. At this point, we know what integration testing is. Now, we need to understand what system testing is? The testing performed on the absolute integrated products to check system compliance with specified requirements on functional and non-functional elements is referred to as system testing.
SIT is also considered as a combination of integration testing and system testing.
User Acceptance Testing (UAT):
UAT (User Acceptance Testing) is conducted at the end of the whole testing process when the product is ready to deliver. The main aim of software development is to develop software that is capable of satisfying the user needs, rather than just fulfilling the system specifications.
UAT is conducted when the product is ready to deliver it is also called as at the end of the whole testing process. UAT is used to validate that the system is acceptable or not.
UAT validates that:
- The developed system fulfills the system requirement specifications
- The system has achieved the performance as documented in the system requirement statement.
- It could vary as defined in the contract.
So come to the table which refers to the necessary comparison:
|Basic of Testing||SIT refers on the interfacing between the modules.||UAT focuses on the requirements with the user point of view.|
|Performed By||SIT is performed by Developers and tester||UAT is performed by Customers and end users|
|Testing order||After unit testing but before system testing||At the end after system testing|
|General issues||Problems like data flow, control flow, etc.||functionality issues or non-working features according to the user requirement.|