- Smoke testing term came from hardware testing, when you get new hardware and power it on if smoke comes out then you do not proceed with testing.
- Smoke testing is done to check the normal health of the build and make sure if it is possible to continue testing. It is done in the beginning of the software testing cycle.
- A subset of most basic and important test cases is selected and run to make sure that most basic and crucial functions of the software are working fine.
- It follows shallow and wide approach where you cover all the basic functionality of the software.
- Smoke test is scripted, i.e you have either manual test cases or automated scripts for it.
- In some organizations smoke testing is also known as Build Verification Test(BVT) as this ensures that the new build is not broken before starting the actual testing phase.
Some basic test cases for Smoke Testing:
- Can you install the software successfully.
- Does software launches successfully after installation.
- When there are some minor issues with software and a new build is obtained after fixing the issues then instead of doing complete regression testing a sanity is performed on that build. You can say that sanity testing is a subset of regression testing.
- Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product. It is done towards the end of the product release phase.
- Sanity testing follows narrow and deep approach with detailed testing of some limited features.
- Sanity testing is like doing some specialized testing which is used to find problems in particular functionality.
- Sanity testing is done with an intent to verify that end user requirements are met on not.
- Sanity tests are mostly non scripted.