SMOKE TESTING:----> Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested. A smoke test is scripted, either using a written set of tests or an automated test Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification). Smoke testing is normal health check up to a build of an application before taking it to testing in depth. SANITY TESTING:-----> A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep. A sanity test is usually unscripted. A Sanity test is used to determine a small section of the application is still working after a minor change. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

Smoke testing is after build releasing we will test high level functionalities working or not. OR                                                SMoke testing:- It is Similar like sanity test this test is conducted to verify are there any issues in Software before releasing to the Test Team.

Sanity testing is we will test all functionalities working properly or not.OR                                                                                      Sanity testing or Build verification test(BVT):- Whenever we receive abuild from development team the basic features of the application is tested to verify the stability of the appication for further testing.