Smoke and Sanity
Can anyone explain what is the difference between smoke and sanity.I am Confused with it .If you say with example it will be really helpful to me.
Re: Smoke and Sanity
These kind of topics are more or less always discussed on a forum. To save time, here is a little advice:
On the top right we have google search facility which will quickly search whatever (relevant) term/ topic needed. It's quick and saves time posting your query.
I tried searching some basic terms/ topics and it was searched quickly.
Smoke Testing is performed after programming work to find out that the basic functionalities of the system is working fine.It is executed "before" any point by point useful or relapse tests are executed on the product build.The reason for existing is to dismiss a severely broken application, so that the QA group does not squander time introducing and testing the product application.After accepting a product work, with minor changes in code, or usefulness, Sanity testing is performed to discover that the bugs have been altered and no further issues are acquainted due with these changes.The objective is to verify that the proposed usefulness works generally of course. On the off chance that rational soundness test falls flat, the fabricate is rejected to spare the time and costs included in a more thorough testing.
Smoke and Sanity testing are the most misunderstood topics in Software Testing. There is enormous amount of literature on the subject, but most of them are confusing. The following article makes an attempt to address the confusion.The key differences between Smoke and Sanity Testing can be learned with the help of following diagram -
1. Both sanity tests and smoke tests are ways to avoid wasting time and effort by quickly determining whether an application is too flawed to merit any rigorous testing.
2. Sanity Testing is also called tester acceptance testing.
3. Smoke testing performed on a particular build is also known as a build verification test.
4. One of the best industry practice is to conduct a Daily build and smoke test in software projects.
5. Both smoke and sanity tests can be executed manually or using an automation tool. When automated tools are used, the tests are often initiated by the same process that generates the build itself.
6. As per the needs of testing, you may have to execute both Sanity and Smoke Tests on the software build. In such cases you will first execute Smoke tests and then go ahead with Sanity Testing. In industry, test cases for Sanity Testing are commonly combined with that for smoke tests, to speed up test execution. Hence it's a common that the terms are often confused and used interchangeably
Both Smoke testing and Sanity testing are type of manual testing. Every Software Testing Company which provides manual testing as QA services performs these both types of testing. Here are the details about Smoke and Sanity testing:
Smoke testing refers to a short series of tests that are executed to make sure that the build appears to be reasonably working and the build is testable. It is executed "before" any detailed functional or regression tests are executed on the software build and immediate after receiving a new build.
After receiving a application build, with minor changes in code or functionality, Sanity testing is performed to ensure that the bugs have been fixed and no further issues are introduced due to these changes. In Sanity testing, we performs module wise in-depth testing. The goal is to determine that the proposed functionality works roughly as expected.
Hope this was helpful and if you have any more doubts.