what is the difference in smoke and sanity testing.?
- 3 Answers
- 5141 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / prashant patil
Smoke Test When a build is received, a smoke test is run to
ascertain if the build is stable and it can be considered
for further testing.
Smoke testing can be done for testing the stability of any
interim build.
Smoke testing can be executed for platform qualification
tests.
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 is shallow and wide.
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
Smoke testing is normal health check up to a build of an
application before taking it to testing in depth.
Sanity testing Once a new build is obtained with minor
revisions, instead of doing a through regression, a sanity
is performed so as to ascertain the build has indeed
rectified the issues and no further issue has been
introduced by the fixes. Its generally a subset of
regression testing and a group of test cases are executed
that are related with the changes made to the app.
Generally, when multiple cycles of testing are executed,
sanity testing may be done during the later cycles after
through regression cycles.
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
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / kumaril mishra
The basic criteria to perform the "Sanity Testing" is to
check the stability of the application build.
Once the build is stable then start the testing based on
features and functionalities.
In case the application build is not stable(inconsistent)
then Smoke Test will come into picture, which is nothing but
the steps required to troubleshoot the problems of the
application build and make the application build from
inconsistent to consistent state.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / giridhar
between this testing just small differnece is there,
depends onthe company testing process.
its all about how the installing step are working properlly.
| Is This Answer Correct ? | 0 Yes | 2 No |
discuss black box and white box testing is not widely used if you disagree tell me why?
when errors occurs in ur script wat will u do
Explain your web application archtechture?
list out types of white box testing with breif explain? some body told seven types are there, plz give me ans. karthis4u@gmail.com
HI Frnds Can u send the openings on 3+ Exp in ManulaTesting in CHennai
What is Orphan links ?
Can anyone please give me the idea how does Requirement Tracebility Matrix, looks like ? or mail me at: ontesting@gmail.com
What are the Risks involved while testing?
4 Answers BT, GL Noble Denton,
What do u do if a bug logged by u is not reproducible in developers environment (developers environment is same as urs)
IS Mutation testin and error seeding the same....if not can anyone tell me the difference???
For Change Password functionality-- Test Case is -- > Change Password Test Steps/Descriptions: 1) Enter Old Password 2) Enter New Password 3) Enter Confirm Password 4) Click on Save button Expected -- > User should login successfully. My question is --> After 4th step tester will check/verify that user [whose password has been changed] is login successfully or not. Should I have to write that steps which user will fallow to verify user login in above test case? What are the preconditions for above test case?
Is dekstop testing and client-server testing same ?
Automation Testing 
