What is the smoke testing and sanity testing..?what is the
difference?
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 |
How do you react when the developer says that defect you logged is not valid?
The following questions were asked me at the HCL...Please try to answer these::: 1Q: For 3rd party fund stransfer through online bankinghow much time it take..? What are the processes behind that..?
write the test senario on opening door in the flow diagram format
What are the essential elements needed for database testing
How many flows of Events are there?
After resolving bug, You immediately do regression testing or later?
1.what is the software life cycle? 2.what tools are available for support of testing during s/w development life cycle? 3.what is s/w development life cycle ? where exuctly the testing activity begin in SDLC?
On Registration Form, if some fields are not mandatory to fill then those fields can accept any invalid input. OR there may have some validation. E.g. Email id field - Not mandatory to fill. If user enter Email id = 453454 should it accept?
What is the exact diff between sanity and smoke test and who will do in real time?
What are the different types of joins
What is comparison testing?
dif b/w localisation and globalisation testing breifly explain ?