smoke vs sanity testing?

My Experience says: Smoke Test - when a build is received, tester is supposed to run quick test to ascertain if the build is stable enough for further testing. It can be done to check the application at base level for the stability of any interim build. Sanity Test - When a new build is given with the minor revisions, instead of doing a thorough regression test, a sanity check is performed. It's generally a subset of regression testing where a group of test cases are executed related to the related area where application has changed. Comparisn: A Smoke Test is scripted --- It may be manual or automated set of Test Cases whereas Sanity Test is usually unscripted. A Smoke Test is designed to touch every part of the application in a cursory way whereas Sanity Test is used to determine small section of the application is working as expected after minor changes. A Smoke test is executed to ensure whether the most crucial functionalities of the application are working but not going into depth whereas Sanity test is a cursory testing, it is performed wehenever requirement mapped testing is required for the changes. A Smoke test is normal health check of a build before going for deapth testing whereas Sanity test is conducted to verify that requirements are implemented correctly in the application.