Interested to Buy Any Domain ? << Click Here >> for more details...
What is the difference between Smoke & Sanity Testing.
- 7 Answers
- 11474 Views
- TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / shweta
Smoke testing is nothing but normal health check to a build
of an application before taking it to the testing in depth.
where as the narrow regression test that focuses on one or
few areas of functionality is what we call as \sanity
testing.
| Is This Answer Correct ? | 12 Yes | 3 No |
sanity testing is nothing but reciving modified buil from
the devalopment team tester 1st time it is the built how to
work common functionalities checking with an appliction is
calld sanity testing
somke testing is nothing but before resele the built once
devalopers check the application is call somke testing
| Is This Answer Correct ? | 9 Yes | 2 No |
Answer / smarty
Smoke testing Is a non-exhaustive software testing,
ascertaining that the most crucial functions of the program
work well, without getting bothered about finer details of
it.
Whereas "Sanity Testing" Is an initial testing effort to
find out if the new software version is performing well
enough to accept it for a major testing effort. For
example, if the new software is crashing the systems every
5 minutes, bogging down the systems to a crawl, or
destroying the databases, then it can be concluded that the
software may not be in a 'sane' enough condition to warrant
further testing in its current state.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / smruti
My ans is smoke testing is done by Developer's team just
before releasing of the Build . And sanity testing is
nothing but Build verification testing done by testing team
after release of build by developers for observable ,
operatable , maintainable, automatable & simplicity of the
build . check it out plz . Thanks !
| Is This Answer Correct ? | 3 Yes | 2 No |
smoke test is performed before testing is conducted in order
to verify the functionality is testable or not, it verifies
the core functionality of the application
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.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / anu
both sanity and smoke testing are done to check whether the build is ready for testing and to check its stability.
But sanity testing is in depth testing that means it covers major and minor functionalities of an app.it is usually done by both developers and testers.this testing done at entry/exit stage of each phase.
smoke testing covers major functionalities and it can be done at any point.
| Is This Answer Correct ? | 0 Yes | 2 No |
Who will prepare the Tracaility Matrix?
Tell me about ur favorite bug.
what is difference b/w Quality assurance & Quality control
Lets say,you are not finished with testing a application,your manager gives you a new task,how do you prioritize your time,what should you do
What are the baselined document needed to create Test case,Integration TEst case, System test case, Acceptance test case?
What is Inter-System Testing? Please answer me frnz!!!
How any person can be a software tester, if he/she is not having software knowledge?
What is boundary value analysis and equivalent partition?
When you found any bug before release product to the customer.what will you do????what will be your aproach?
How do u test any "web-site" as a secure site...? or How do you test the security of a web-site...?
What is exploratory testing?
Hi i am looking for Test Engineer Job, i have done the course, but i don't have work experience on it, Is it So important to have real time Exp or knowledge is enough? and please let me know like how i can improve for the interview. You can send me a mail on this id: rashmi_vastred@yahoo.co.in
Automation Testing 
