|
What is the difference between Smoke testing and
Sanity testing?
Smoke testing is after build releasing we will test
high level functionalities working or not. Sanity testing is we will test all
functionalities working properly or not.
Sanity Testing: Teswt Engineer cover basic functionality of the buld to
validate " whether the build is stable for complete testing or not"
Smoke Testing: It is an extra shakeup in sanity process.
In this tesing, testing team rejects build with specific reasons where that
build is not working
sanity testing is an Initial effort to check whether the application can be
tested further without any interruption. Basic gui functionality,connectivity to
database are concentrated here.
Smoke Testing:Its confusing question and answer too.
It covers most crucial functions of the application..
testing carried out check whether most crucial functions of the application
work fine or not? dont bother about the in-depth coverage of each testset.
what are most crucial functions in the build, you should know it before
coming to testing phase. or your manager will write a seperate high-level
testcase for that.
Sanity Testing:-Tester conducts the Sanity test to ensure the stability of
the application build.Tester finds weather the application build is stable for
complete application or not.
Smoke Testing:-It covers the major functionality of the application without
bothering with finer details.
Conceptually Smoke testing and sanity testing both are same,but
perceptionally these are different.Smoke testing:Smoke testing is conducted with
negative perception,it is the testing in which all the functionaliteis are
avaliable are not is tested , to proceed for further overall testing.Sanity
testing: This is also test for to check whether all the functionaliteis are
available are not.But this testing is conducted with positive perception.
|
|
Smoke |
Sanity |
|
1 |
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 sanity test is a
narrow regression test that focuses on one or a few areas of
functionality. Sanity testing is usually narrow and deep. |
|
2 |
A smoke test is
scripted--either using a written set of tests or an automated test |
A sanity test is
usually unscripted. |
|
3 |
A Smoke test is
designed to touch every part of the application in a cursory way. It's
is shallow and wide. |
A Sanity test is
used to determine a small section of the application is still working
after a minor change. |
|
4 |
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 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. |
|
5 |
Smoke testing is
normal health check up to a build of an application before taking it to
testing in depth.
|
sanity testing is
to verify whether requirements are met or not,
checking all
features breadth-first.
|
|