Exact Difference between Sanity and Smoke Testing
- 6 Answers
- 8017 Views
- Virtusa, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Sanity and Smoke testings are very basic leavel testing in
STLC,this testing is also know as TAT(Tester Acceptance
Test).
Sanity Test:- Testing the Project/Product for cheacking
weather the project/Product is able to test the basic
functionality of the application or not.
Ex:-If the project is on google Search,first we have to
check weather the search box,submit button is present in
the application or not.
Smoke testing: Testing overall application to check all the
main functionalityes are present in the application or
not,If present they are stayable enough to test or not.
Correct me if i am wrong..
M.V.K.Chaitanya Rao
mvkrishnachaitanya@gmail.com
9963907370
| Is This Answer Correct ? | 9 Yes | 0 No |
Answer / tulasi srinivas
To my understanding: The objective of both these tests are
almost same. The ends at which they are performed are
different.
Smoke testing is done on the changed and existing code of
application, before it is checked in to the Version control
system and release marked to QA. Hence this is done at the
Development end.
Sanity testing is done in the areas of new fixes given as
well as existing functionality of the system - to assess
whether a release can be accepted for QA. Hence this is
done at the QA End.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sudha
• 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.
• 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.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / chennamsubbaraidu
Chaitanya rao sir, i didnt understand the Exact
Difference.can u explain me clearly?
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / samratreddy
Smoke Testing:this testing is conducting all funtionalities
correctly working r not,should be present in the
application r not.
sanity testing:this testing conducting the application
properly working r not.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / sumanth
Smoke Testing: This testing is detailed testing.It is
conducted on the application to check whether all the
functionalities are supposed to be present in the appl are
really present or not.
Also to check the functionalities are "NORMAL"
Sanity Testing: This is not detailed testing. This testing
is done to check whether the appl is proper for testing or
not.
| Is This Answer Correct ? | 1 Yes | 3 No |
what is the diff between function and Sub function
What is the testing lifecycle and explain each of its phases?
Can anybody find the bugs in this "allinterview.com" site???
What is client server application testing?
What is the difference between the test scenarios and test strategy?
what is the combination of grey box testing
what is the severity we give. login fails eventhough we enter the correct username and pwd.
what is the use of testing? is testing compulsary
What is Gap Analysis?. Is there any template for it.Describe briefly about Gap Analysis Please
suppose i received 3 build b1, b2, b3 on which build i will do regression testing
1.Acceptance testing involves procedures for identifying acceptance criteria for interim life cycle products and for accepting them.is that? 2.Acceptance testing occurs only at the end point of the development process; it should be an ongoing activity that test both interim and final products.is it?
can any one give the example for high severity high priority high severity low priority low severity high priority low severity low priority
Automation Testing 
