19. Difference between System and Integration Testing?

System Integration Testing(SIT) 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 tested modules together. This could be at a webshop: website-frontend + logic + db + ordering-api. Testing would include if the order done in the front-end (on the website) is correctly passed through all stages to the ordering-api.

"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.