Testing - Genaral

Differences

Sanity testing:

- Performed after receiving a softwware build with changes in code/functionality (fix bugs, implement new functions, changes server,...) => ascertain that bugs have been fixed/new functions have been implement and no further issues are introduced due to these changes.

- Goal: determine that the proposed functionality works roughly as expected. ( not to verrify thoroughly the new functionality)

Smoke testing:

- Performed after receiving a software build => ascertain that the critical functionalities of program is working fine.

- Executed before detailed functional or regression test.

- Gold: reject a badly broken application, verify that the critical functionalities are working fine.

Differences:

Smoke TestingSanity TestingTo ascertain that the critical functionalities of the program is working fineTo check the new functionality / bugs have been fixed without further issues.To verify the "stability" of the system.To verify the "rationality" of the system.By the developers or testersBy testersUsually documented or scriptedNot documented and is unscriptedSmoke testing is a subset of Regression testing.Sanity testing is a subset of Acceptance testingSmoke testing exercises the entire system from end to endSanity testing exercises only the particular component of the entire systemSmoke testing is like General Health Check UpSanity Testing is like specialized health check up