What is Smoke Testing?

Smoke Testing is performed after software build to find out that the critical functionalities of the program is working fine. It is performed “before” any detailed functional or regression testing on the software build. The purpose of this testing is to discard any broken application, so that the QA team does involve and waste time in installing and testing the software application.

In this, the test cases selected cover the important functionality of the system. The objective is not to perform in-depth testing, but to verify if the critical functionalities of the system are working fine.

In computer programming and software testing, smoke testing (also confidence testing, sanity testing,  build verification test (BVT) and build acceptance test performed on Appium Tutorial) is preliminary testing to reveal simple failures severe enough to (for example) reject a prospective software release. Smoke tests are a subset of test cases that cover the most important functionality of a component or system, used to aid assessment if main functions of the software appear to work correctly. When used to determine if a computer program should be subjected to further, more fine-grained testing, a smoke test may be called an intake test. Alternately, it is a set of tests run on each new build of a product to verify that the build is testable before the build is released into the hands of the test team. In the DevOps paradigm, use of a BVT step is one hallmark of the continuous integration maturity stage.