Education and Career Forum

what is the difference between smoke and sanity testing?

Please reply

Difference between Smoke and Sanity Testing ?


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 designed to touch every part of the application in a cursory way. It's is shallow and wide.

- Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

- A smoke test is scripted, either using a written set of tests or an automated test.



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 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.

- A sanity test is usually unscripted.

hello friend.......
according to me......

Sanity testing: to verify the stability of the application to conduct the total testing or not.

Smoke testing: when we receive a new build on new version we will validate whether all critical functionalists are working properly or not and verify the application is stable or not.

smoke test is done as soon as new build is released and this is done test engineer.
After smoke test is done then sanity test comes to picture.

Smoke Testing is performed after developing the software to ensure the specific functionalities are working properly.This test is performed before it is executing functional or regression test by QA team.

Sanity Testing performed after making changes to fix bugs in the software that are found.This test is to ensure whether the changes has effected the functionalities of software.

Smoke Testing: This testing is done every time a new build is given to testing team.
Simply this is done to check whether further testing on the application can be done or not.
Example-application is having blocker defect like unable to login, so further testing cannot be done.
Remember only positive testing is done here that too on only major or critical modules.

Sanity Testing: Testing done in depth where each and every functionality of a particular module is tested. Here both type of testing positive and negative are done.
This testing is generally done after application is some what stable.