Interested to Buy Any Domain ? << Click Here >> for more details...
what are the differences between smoke and sanity testing
- 1 Answers
- 3937 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 |
hi can anyone provoide SRS for order processing system and intranet plz
which software company allowed industrial visit in chennai?
explain the methodologies / ways to create the test cases for QA
How would you finalize on testcases in estimation? Say you have 200 requirements. How would you come up how many testcases you are going to write for each requirements?
Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?
How does agile communication differ from tradition software engineering communication? How it is similar?
Any body wants to learn qtp (Automation testing)? on Banking domain with realtime implementations
explain the basic QA plan to co-op with development plan for effective delivery of the product
how to test the application/software without any requirements(like BRD,FRD etc.,) for a new project?
what are the new trends / methodologies in QA for SW product testing
what are the basic knowledge requirements for a QA engineer to start QA of a specific product
compare all the models of software development. write advantages and limitations of each.
Requirement Management 
