Smoke Testing

The concept of smoke testing went from engineering environment:

"With the commissioning of new equipment (hardware), it was thought that the testing is successful, if the installation did not go to smoke."
In the same test software, it is used for surface inspection of all application modules for efficiency and the availability of fast and blocking the found critical defects. Subspecies of smoke testing is Build Verification Testing and Acceptance Testing, performed at the functional level testing team, which resulted in a conclusion that is accepted or not the installed version of software testing, operation, or for delivery to the customer.

For ease of operation, saving time and human resources it is recommended to implement automated test cases for smoke testing.

Sanity Testing

Sanity testing - a narrow-tested enough to prove that a particular function works according to the stated specification requirements. Is a subset of regression testing. Used for assessing the performance of certain parts of the application after the changes made in it or the environment. Usually performed manually.

Unlike the sanitary testing of smoke (Sanity vs Smoke testing)

Some sources mistakenly believe that health and smoke testing - it’s the same thing. We believe that these kinds of tests have "motion vector" directions in different directions. Unlike smoke (Smoke testing), health testing (Sanity testing) is directed inwards tested functions, while the smoke is directed in breadth, to cover the tests as many as possible of the functional as soon as possible.

You would..
Share
Related Documents
  1. Smoke Testing vs Sanity Testing (1531)
  2. Smoke testing (451)
  3. Software Testing Fundamentals (1124)
  4. Smoke testing in existing system (966)
  5. Lessons Learned From Smoke Testing (1030)
  6. Difference between Smoke and Sanity Testing (824)
  7. Smoke and sanity testing (584)
  8. [Test Case] Smoke Testing Test Case Template (8777)

Written by

Mathi,

Testing executive