Interested to Buy Any Domain ? << Click Here >> for more details...
what are the differences between smoke and sanity testing
- 1 Answers
- 3981 Views
- I also Faced
- E-Mail Answers
Answer / sevak.yatrik777
Smoke Testing: Software Testing done to ensure that whether
the build can be accepted for through software testing or
not. Basically, it is done to check the stability of the
build received for software testing.
Sanity testing: After receiving a build with minor changes
in the code or functionality, a subset of regression test
cases are executed that to check whether it rectified the
software bugs or issues and no other software bug is
introduced by the changes. Sometimes, when multiple cycles
of regression testing are executed, sanity testing of the
software can be done at later cycles after through
regression test cycles. If we are moving a build from
staging / testing server to production server, sanity
testing of the software application can be done to check
that whether the build is sane enough to move to further at
production server or not.
Difference between Smoke & Sanity Software Testing:
* Smoke testing is a wide approach where all areas of
the software application are tested without getting into too
deep. However, a sanity software testing is a narrow
regression testing with a focus on one or a small set of
areas of functionality of the software application.
* The test cases for smoke testing of the software can
be either manual or automated. However, a sanity test is
generally without test scripts or test cases.
* Smoke testing is done to ensure whether the main
functions of the software application are working or not.
During smoke testing of the software, we do not go into
finer details. However, sanity testing is a cursory software
testing type. It is done whenever a quick round of software
testing can prove that the software application is
functioning according to business / functional requirements.
* Smoke testing of the software application is done to
check whether the build can be accepted for through software
testing. Sanity testing of the software is to ensure whether
the requirements are met or not.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain the architecture diagram of your current project?
Any body wants to learn qtp (Automation testing)? on Banking domain with realtime implementations
can you suggest me the industrial visit for BE/BTECH/MCA/MSC/ME students in Chennai?
what are the priliminary expectations from smoke testing from developer and QA point of view
anybody wants the industrial visit in chennai and banglore,kindly contact me?
which electronic company offered industrial visit in chennai?
What are the advantages and disadvantages of developing software in which quality is "good enough" ? ie. What happens when we emphasisdevelopment speed over product quality?
Are there characteristics of a system that cannot be established during system engineering activities? Describe the characteristics, if any, and explain why a consideration of them must be delayed until later engineering steps.
what are the differences between product branch qualification as well as product qualification !!! if a product branch supports more than a product then what is the QA strategy towards the same
How does development of software differ from that of hardware from a quality viewpoint?
What are the beta test and alpha test?
Why is it that a single, all – encompassing metric cannot be developed for programme complexity or programme quality?
Requirement Management 
