Quality Testing

Quality is delighting customers

Difference between Smoke Testing and Sanity Testing ?

Hi Friends,

What is the exact difference between Smoke Testing and Sanity Testing ?

Is smoke testing just the testing of the build to check its main functionality and sanity testing is the in-depth testing of any functionality. Do we don't prepare and execute any test case for smoke testing and do execute them for Sanity Testing? We simply reject the build during smoke testing without continuing testing any further ?

Kindly clear my doubts and if these are correct please also mention other differences.

Thanks in advance.

Regards,
Divya

Views: 200

Reply to This

Replies to This Discussion

Smoke testing and sanity testing - Quick and simple differences

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
•A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
•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 a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
•Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

This is taken from http://onestoptesting.com....

Regards,
Himanshu Patel
Sanity Testing:-Tester conducts the Sanity test to ensure the stability of the application build. Tester finds weather the applications build is stable for complete application or not.

Smoke Testing:-It covers the major functionality of the application without bothering the details.
I totally agree with Himanshu,



Thanks
Somke ttesting mail perpose is our build is stable for further testing.
Sanity testing main perpose basic functionality check before release final build.
Smoke Test:
When a build is received, a smoke test is run to ascertain if the build is stable and it can
be considered for further testing.
Smoke testing can be done for testing the stability of any interim build. Smoke testing
can be executed for platform qualification tests.
Sanity testing:
Once a new build is obtained with minor revisions, instead of doing a thorough
regression, sanity test is performed so as to ascertain the build has indeed rectified the
issues and no further issue has been introduced by the fixes. It’s generally a subset of
regression testing and a group of test cases are executed that are related with the changes
made to the app.
Generally, when multiple cycles of testing are executed, sanity testing may be done
during the later cycles after thorough regression cycles.
Smoke
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
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.
deep, is tested.
Sanity
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.
Smoke
A smoke test is scripted--either using a
written set of tests or an automated test
Sanity
A sanity test is usually unscripted.
Smoke
A Smoke test is designed to touch every part
of the application in a cursory way. It's is
shallow and wide.
Sanity
A Sanity test is used to determine a small
section of the application is still working
after a minor change.
Smoke
Smoke testing will be conducted to ensure
whether the most crucial functions of a
program work, but not bothering with finer
details. (Such as build verification).
Sanity
Sanity testing is a cursory testing; it is
performed whenever a cursory testing is
sufficient to prove the application is
functioning according to specifications.
This level of testing is a subset of
regression testing.
Smoke
Smoke testing is normal health check up to a
build of an application before taking it to
testing in depth.
Sanity
sanity testing is to verify whether
requirements are met or not, checking all
features breadth-first.
Sanity Testing :
It is a type of testing in which one will perform overall testing on the released build in order to check whether the build is proper or not for conducting detailed testing.

Usually one will check the following during this type of testing:
1. Whether the build can be properly installed or not.
2. Whether one can navigate(travel) to all the areas of the application or not.
3. Whether all the important features are available or not.
4. Whether the required connections are properly established or not.

Some companies even called this type of testing as Smoke testing but some companies will say just before releasing the build the developers will check whether build is proper or not that is known as Smoke testing and Once the build is released once again the test engineer will check whether the released build is proper or not that is known as Sanity Testing.
I m confused :(

In Smoke testing test cases are needed or not ? and same about Sanity Testing ?
Divya,

Yes..Obviously we should have set of testcases for Smoke Testing(Its from most of P1 Testcases) and Sanity Testing.

Regards,
Somanathan R.

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service