Theoretically, there’s a small difference between smoke test and sanity:
*Smoke test is often a test suite used to evaluate if the build is good enough further testing. The idea of this test is find critical problem early and reject the build so that we don’t waste time to test further (the broken build). More often, this test is performed right after you receive the build from developer.
*Sanity test is often a test designed to test a specific feature/bugs of a build just to evaluate if the feature/bugs works as expected. The idea of this test is also detect problem as soon as possible before further testing.
However, in reality, people use smoke test and sanity interchangeably which is the first test performed when a build is released for testing so that test team can detect early bugs as soon as possible.
Another name for smoke test/sanity test is Build Acceptance test or Build Validation Test…
Anyway, there’s no need to worry about this difference. It’s just the matter of terms usage.
Hey Suri,
Theoretically, there’s a small difference between smoke test and sanity:
*Smoke test is often a test suite used to evaluate if the build is good enough further testing. The idea of this test is find critical problem early and reject the build so that we don’t waste time to test further (the broken build). More often, this test is performed right after you receive the build from developer.
*Sanity test is often a test designed to test a specific feature/bugs of a build just to evaluate if the feature/bugs works as expected. The idea of this test is also detect problem as soon as possible before further testing.
However, in reality, people use smoke test and sanity interchangeably which is the first test performed when a build is released for testing so that test team can detect early bugs as soon as possible.
Another name for smoke test/sanity test is Build Acceptance test or Build Validation Test…
Anyway, there’s no need to worry about this difference. It’s just the matter of terms usage.
Hope it helps.