Thread: Sanity testing is same to smoke testing ?

I have read all answer and i am convinced but regarding to Sanity testing , Sanity testing is same to smoke testing ? pl explain difference with example in steps
thanks

hi hithesh,

I Repeat there is no such differences between smoke and sanity testing

Thanks
Deepasree

hi hitesh,

Smoke test in the sence we follow the application by using mandatary vaues until end page with out any discripences..

same for sanity testing also...

Thanks and regards,
Bhaskar kumar

Originally Posted by hitesh_shah19

I have read all answer and i am convinced but regarding to Sanity testing , Sanity testing is same to smoke testing ? pl explain difference with example in steps
thanks

Sanity or smoke testing has a specific reference. It's not any testing, but it is the testing that is done immediately after a deployment (or code drop) into an environment, and before using the dropped code for the purpose it was dropped.
Example:
Code drop to test environment - Once the code drop occurs, the sanity or smoke testing (at times also known as shake out) occurs prior to actual quality testing begins.
Code drop to production environment - Once the code drop occurs, the sanity or smoke testing occurs prior to declaring "Deployment Complete" and releasing the systems to production/customer use.

The purpose of this kind of testing is to make sure all the code that needed to be dropped has actually dropped, all the permissions have been set correctly, and there are no environment/access glitches. This is not a functionality test, rather a high level sanity check to make sure everything we did during the drop process has actually gone thru, and when the actual users try to use the application, they can.

hi hitesh,

As Deepasree mentioned, there is no difference between sanity testing and smoke testing.

Smoke Test (a.k.a sanity check or acceptance into testing)

Thanks
Sushma

According to my understanding, Sanity testing and smoke testing are very different; in that smoke testing is done to verify that key functionalities of an application are working as expected without going deep into the application, while sanity testing involve narrow and deep testing a section of functionalities of an application. Sanity testing focuses on few areas of functionalities