smoke testing is test whether the build is installed
properly or not and is ready for further major testing.
Sanity testing is carried after smoke testing to check
whether the major functionality is working properly or not
to proceed further testing.
for ex: when a build is passed the smoke test, the sainty
test is conducted on it by just navigating to the hyper
links,or major functional whether the links are opening
properly or not.Here there is will be using more critical
test cases for testing the Sanity testing.
Smoke testing:
To test the basic parts of the application whether it is
stable for major testing
Sanity testing :
To test the major functionalities of the application whether
it working properly or not
Murali
dharanmu@yahoo.com
Sanity and smoke testing, both are same.
Somke testing done on Development phase before going to QA
Environment.
Sanity Testing done in Testing Phase (QA) , when build came
to QA Environment.
If i am wrong please correct me...
Sanity testing is useful for checking for the basic
funanality of the application.
Smoke testing is useful for checking for the main
funanality of the application.
hi rajeshwar rao
i think ur ans is different from the process actually
said ...
smoke is used to check the basic funtionality and sanity
is used for major functionality.
Sanity test:
Sanity test is also called as test accesptance test and it
it will be done to check whether the application is coming
for testing full filling the requirements or not. which it
supposed to have
Smoke testing:
Smoke tsting is conducted after sanity testing, the
purpose is whether there is any danger or smoke if we
accept application for test.
Sanity test testing is done positive perception and smoke
testing is done negative perception
Smoke testing :
We can otherwise call it Horizontal/Breadth Testing.
Here we check all the major functionalities of the AUT.
Sanity Testing:
It is known as Vertical/Depth testing.
Here we check the sub-functionalities of the major
functionalities.
The difference between smoke and sanity testing is in smoke
testing tester concentrate on the major functionality of
the application whether it is working or not for further
functionality. eg. build crash, environmental effect,
networking etc..
where as in sanity testing basic functionalities are
tested. eg. check boxes,radio buttons, text boxes, list
boxes etc..
Sanity testing is testing the new version is working better
than the previous version.
Smoke testing is running the application to know the flow &
functionality of the application.
Sanity testing means whether the build is ready for further
testing or not.
Somke testing means whether the build is ready for release
or not.
If Tester found the bug in build 2.0.0 tester will assign
it to developer but not get fixed in next build 2.0.1 then
tester have to assign it again for every build if not get
fixed upto build 2.0.7 or not?
Same question is for version also?