What is Smoke Testing?

SMOKE TESTING

The name Smoke comes from hardware testing (electrical) looking for smoke when powering electrical items for the first time.

A smoke test may address basic questions like :

     1. Does the program run?
     2. Does the user interface open?
     3. Does clicking the main button do anything?

* The term originates in hardware repair and has been applied to software.

* It is intended to be a quick test to see if the application "catches on fire" when run for the first time.

* It is just to make sure you don't waste a bunch of folks time by setting them loose on something that's obviously broken.

* In software testing, smoke testing also know as :

1. Confidence testing
2. Sanity testing
3. Build verification test (BVT)
4. Build acceptance test.

* This is the first testing on the initial build.

* The process of smoke testing aims to determine whether the application is so badly broken as to make further immediate testing unnecessary.

* It aims to ensuring that the most important functions work. It is used to decide if a build is stable enough to proceed with further testing.