Interested to Buy Any Domain ? << Click Here >> for more details...
what are the differences between smoke and sanity testing
- 1 Answers
- 3904 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
How would you know if the same build you tested is deployed in production? There are chances that developer might deploy some other working build?
what is the difference configurable items and non configurable items ?
Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?
is all the test cases to be automized !!! if yes / no let explain the reason
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?
what are the usual metrics one have to apply for SW improvement projects
Hi Friends... I faced an question in Tcs.But i unable to answer. find the question below.. A root filesytem"c0t0d0s0" caries 100 gb data. in this filesystem. i am having 3 files named a,b,c it caries 20 gb data each. I need to take backup only 3 files a,b,c. How i can take. Note you need to take only 3 files to an single tape having capacity 80 gb. Whats the commad used?
Give a suitable definition of software quality and briefly describe the rationale for your definition.
Explain the deployment process?
brief about the methodologies to evaluate weightage of test cases and what are the basic parameters to be considered
As soon as you get a build ,what would you ask your testing team to do?
How would you finalize the number of resources/testers needed for the testing in the estimation ?
What are the negative test cases for water bottle?
Why is it that a single, all – encompassing metric cannot be developed for programme complexity or programme quality?
What are the main objectives of configuration management and version control?
