What is the difference between sanity testing and smoke
testing
Answers were Sorted based on User's Feedback
Answer / ravinder.yalla
smoke testing: It is performed by developers before
releasing the application to testing team.In this they
verify basic functionality of an application
sanity testing: After receiving the application test
engineer VALIDATES basic functionality of an application
with help of checked list to estimate stability.
Ex: For login screen
Smoke testing is only test whether the user is able to
login or not .
And Sanity testing is to test text field lenght,datatype of
text,which page it takes
Is This Answer Correct ? | 4 Yes | 2 No |
Answer / smita
Smoke testing is done to ensure that build is stable and
key features r working porperly without going in depth.
Sanity testing is subset of regression testing and it is in
testing the build in depth.
e.g For login screen
Smoke testing is only test whether user is able to login
and Sanity testing is to test text field lenght,datatype of
text,which page it takes.
Is This Answer Correct ? | 1 Yes | 0 No |
Hello Srinivas,
This question was asked by our allinterview users many
times..
Here are the URL's.. pls go through it.
http://www.allinterview.com/showanswers/421.html
http://www.allinterview.com/showanswers/3670.html
http://www.allinterview.com/showanswers/3860.html
http://www.allinterview.com/showanswers/6518.html
http://www.allinterview.com/showanswers/9527.html
Pls. search ur question using "search" and if u not found
any stuff then onlu post again..
Pls cooperate
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / patilvis
Smoke :- 1)Checking the testability of the s/w termed as
smoke
2)Also know as a bulid verifiction testing / basic
functional testing / link testing
3)smoke test can eithe be performaed manually or using an
automates tools.
Sanity:- 1)checking behavior of the sys is termed as sanity
testing
2)also called as narrow regression testing
3)considered as subset of reqression testing
4) sanity testing is a focused narrow and deep but cursory
5)sanity test are useful both for initial enviroment
validation & future interactive increment.
Is This Answer Correct ? | 0 Yes | 0 No |
hai....
Smoke testing:
Basic functionality for stability of product for further
level testing
Sanity testing:
check out the old build for the issues were fixed in the
bug fixed stage and check no issues were raised after
issues fixing
k byee.
B.Ramyasri
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / nitin kanchan
Smoke testig: checking all the links and tabs in an
application are working correctly or not.
open,close,Account, user etc.
Sanity testing: basic functionality are working or not. ex
account create,transaction done, account change etc.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / prasanna_ny
Sanity testing:Sanity testing is testing the application to
ensure, if it is stable enough to continue further
testing.If the test fails ,we cannot continue testing
further.Sanity testing is the initial test after the build
release.It is done by the QA team.
Smoke testing:This is done by the developers , to ensure
that the build is ready for release to the testing team.
Is This Answer Correct ? | 6 Yes | 7 No |
Answer / saroj kumar sahoo
Smoke Testing is build is stable or not.It is done by dev.
side.
Sanity Testing is product is stable or not.It is done by QA
(Tester)
Saroj Kumar Sahoo
Is This Answer Correct ? | 0 Yes | 1 No |
who is perform user acceptance testing and when it will conduct? is it before alpha testing or after alpha testing? Please post the answer as soon as possible
What is a test condition wen a tester will prepare or write a test condition?
Difference between Test Plan & Test Strategy?
What's an 'inspection'?
what are the conditions of test cases?
Write test cases to anti virus software?
How you will test media player ?
What is meant code review?
Any one please tell the adhoc testcases for Gmail application?
what do you mean by documentation testing
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?
Does we make documentation for all defects?