Smoke & Sanity

Difference between smoke and sanity testing? Who perform smoke an sanity testing?

Whenever there is any change (mainly addition or deletion of any functionality) these smoke and sanity testing required.
Developer does smoke testing to confirm that the build is working good with new feature.
Tester do sanity testing to see that application is sane enough to do exhausted testing.

Whenever we made a Change or Modification we perform Regression Testing !!!
Smoke testing to confirm that the build is working fine with its added features which will be performed by Tester may includes developer presence !!!
Sanity testing to verify that application is good enough to outdo the next stage like Execution of Test Cases !!!

SANITY TEST - Brief test of major functional elements of a piece of software to determine if its basically operational. Sanity testing is a preliminary check of functionality prior to execution of a comprehensive test suite.

SMOKE TEST - is similar, but a quick-and-dirty test that the major functions of a piece of software work. 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 on fire.

I want lit bit clearly,
what is sanity and smoke testing?

both are done by test engineers only....

[I]Smoke Testing and Sanity Testing are the processes of
checking the basic functionality of the application. These
testing are done before the application is cleared for in
depth testing.
[/I]