After receiving a software build, with minor changes in code, or functionality, Sanity testing is performed to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
Stress testing involves subjecting the program to heavy loads or stresses. This should not be confused with volume testing; a heavy stress is a peak volume of data encountered over a short span of time.
Shakeout Test / Shakedown Test/Smoke Test
A quick test of the main portions of a system to determine if it is basically operating as expected, but avoiding in-depth testing. This term is often equivalent to Smoke Testing.
Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.An orderly progression of testing in which software and/or hardware elements are combined and tested until the entire system has been integrated
System Testing is done to explore system behaviors that can’t be done by unit, component, or integration testing. Example, testing: performance, installation, data integrity, storage management, security, reliability. Ideal system testing presumes that all components have been previously, successfully, integrated. System testing is often done by independent testers.