Smoke v/s Sanity Testing
There is a vast confusion between Smoke and sanity testing; Sundry people still have muddle between these terms. But there is a meek and comprehensible difference between the two.
- Smoke testing instigated in the hardware testing practice of whirling on a new piece of hardware for the first time. In software industry, smoke testing is a narrow and extensive approach whereby all areas of the application without getting into too deep, is tested.
- It is well scripted, either using written routines of tests or an automated test.
- A Smoke test is intended to touch every part of the application in a brief manner.
- Smoke testing is conducted to ensure whether the most essential roles of a program are working but not considering the deep details.
- Smoke testing is like a normal health checkup in order to build an application before taking it to testing in depth.
Now let us give you a glimpse of other fundamental testing terms called “Sanity Testing”.
- Sanity test is a slight deterioration test that focuses on few areas of functionality. It is usually narrow and deep.
- A sanity test is typically impulsive.
- A Sanity test is used to govern a small unit of the application is still working after a minor alteration.
- Sanity testing is also brief testing; it is performed whenever a cursory testing is adequate to prove the application is functioning according to specifications.
- Sanity testing is to confirm whether the requirements are met or not, checking all features.