What is the smoke testing and sanity testing..?what is the
difference?
- 10 Answers
- 17685 Views
- TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / samuel
Both have stated two different views so pls some on infrom
the correct answer
| Is This Answer Correct ? | 2 Yes | 0 No |
Build Aceptance testing or Build Verification testing or
Sanity testing:
It is a type of testing inwhich one will
conduct overall testing on the already released build
inorder to conform whether the build is proper or not for
conducting detailed testing.
Ususlly they check the following during this type of
testing
1. Whether the build can be properly installed in to the
environment or not
2. Whether one can naigate to all the parts of the
application or not
3. Whether all parts of the important features are
available or not
4. Whether the required connections are properly
established or not.
In some companies this is also called
as 'Smoke testing', but some compaies say that just before
releasing the build the developers will conduct overall
testing inorder to conform whether the build is proper or
not that is known as 'Smoke testing' and once the build is
released whether the test engineers are doing the build is
known as 'Build Acceptance testing or Build Verification
test or sanity testing'
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / vidhi
Smoke testing is to test the main function of every feature
of the built. Sanity testing is to test the every feature
of the built
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / santoshnathan
Sanity testing :This is a type of initial testing performing
on application and make sure that it has no blockages.
Blockages in the sense whether the all functionalities are
avialable or not in order to perform detailed testing on the
application.
Smoke Testing:This is also a type of initial testing
performing on application in order to test whether it is
stable or not.
But companies are following either one.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ramesh kr.
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).
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
| Is This Answer Correct ? | 1 Yes | 1 No |
Sanity: Initial Testing is conducted to ensure that every
link is working correctly or not, to proceed for testing.
Smoke: when the build is tested, the total is build is
tested again overall to ensure every thing is working
correct.
****Some companies say both are same*****
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / prathijna
Differences b/w Smoke Testing & Sanity Testing:
i) Testing the basic and critical features of an application before doing thorough or rigorous testing is known as smoke testing where as Sanity testing is a subset of acceptance testing and it is also subset of Regression testing.
ii) Smoke testing is shallow and wide testing where as in Sanity is Narrow and deep testing
iii)In smoke testing we do positive testing and write smoke test cases where as in Sanity testing we do both positive and negative testing and we don't write sanity test cases.
iv) In smoke testing we go for automation testing and where as in sanity testing we don't go for automation testing.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sunil reddy
smoke testing is conducted to ensure that application is
stable or not 4 further testing.
Sanity test is used to validate all major functionalities
| Is This Answer Correct ? | 3 Yes | 4 No |
Answer / kris
sanity testing is seeing if the application is fit enogh
for actual testing. eg: testing the weblink,browser etc.
smoke testing is testing the major functionalities in the
entire application. otherwords..,checking here and there
and get a feel of the whole system regarding the
functionality.
| Is This Answer Correct ? | 3 Yes | 7 No |
what is the challenging position faced in the testing not in point of management point of view it must be in the point of while testing the application?
What is workadround
How can you find dead code!!
2. What resources do you use to learn about Web accessibility?
is it necessary to write neagtive test cases for each and every field
what is the entry criteria and exit criteria of integration testing?
How can data caching have a negative effect on load testing results?
Hello can anybody list out supported and unsupported browsers for Window OS,Android OS,MAC OS Ubuntu
If I want to do a version testing then how can I do it? Is there any difference between 1.0 & 1.0.0.0 version?
What are the Level of Severity
11 Answers Atlantic Scientific, Deloitte,
Hi all, Can u pls help me with some Testing mannual for Test case preparation, Test planning and for attending ISTQB Examination. Kindly provide your feedback in this mail id (gbijesh@gmail.com) Tnks & Rgds Bijesh G
My application is Central Management System(CMS) & Point of Sale(POS). CMS - main server is installed on one PC & POS - Client is installed on another PC. We can manage number of POS from CMS server. CMS is divided into CMS-Master & CMS Client. System flow is like - Manage data Menu has 22 submenus ex: Users, Customers, Printers etc....................... Manage all 22 submenus in CMS-Master Import all 22 submenus in CMS-Client one by one. My Question ---> Import CMS-Master to CMS-Client is the test case, So Should I consider it as a single test case or I have to write separte test cases for Importing All 22 submenus?
Automation Testing 
