Smoke Testing vs Sanity Testing

The below comparison table enlightens the important differences between smoke testing and sanity testing in a quick manner:

S.No.	Comparison Basis	Smoke Testing	Sanity Testing
1	Test coverage	It is a broad approach to testing where all parts of the application are tested.	It is a narrow approach to testing where specific parts of the application are tested.
2	Measures	It measures the stability of the system by performing rigorous testing.	It measures the rationality of the system by performing rigorous testing.
3	Technique	Smoke testing can be either manual or automated.	Sanity testing can be done without test cases or scripts.
4	Executed by	It is performed by both testers and developers.	It is performed by only testers.
5	Purpose	Testing is done without getting into deep but whenever needed tester has to go into deep.	Sanity testing does not need to go into deep of the application.
6.	Performed at	Smoke testing is the first testing performed on the initial build.	Sanity testing is performed when the build is comparatively stable.
7	Documentation	Smoke testing is documented.	Sanity testing is not documented.
8	Used to	It is used to test End to End function of the application.	It is used to test only modified or defect fixed functions.
9	Subset	It is considered as a subset of acceptance testing.	It is considered as a subset of regression testing.