Smoke vs Sanity Testing

Smoke Testing	Sanity Testing
build verification test	tester acceptance testing
executed "before" any detailed functional or regression tests [~new features added to system, then test system again] are executed on the software build	after receiving a software build
purpose is to reject a badly broken application	If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous [~strict] testing
ascertain [~determine] that the critical functionalities of the program is working fine	check the new functionality / bugs have been fixed
The objective of this testing is to verify the "stability" [~constancy] of the system in order to proceed with more rigorous testing	The objective of the testing is to verify the "rationality" [~reasonableness] of the system in order to proceed with more rigorous testing
performed by the developers or testers	performed by testers
documented or scripted	not documented and is unscripted
a subset [~a set within a larger set ] of Regression testing	a subset of Acceptance testing
exercises the entire system from end to end	exercises only the particular component of the entire system
like General Health Check Up	like specialized health check up