Smoke testing is a testing methodology oriented on detection primary errors and inconsistencies in software in the early stages of product development. Some developers underestimate this type of testing, but statistics show that it is quite profitable.

If developers want plainly to affirm a concept of the software under design they certainly need the smoke testing to be performed. This kind of verification is akin in its main target with functional testing, as far as both of these methods should check the functional. But smoke testing is more oriented on the critical system parameters, which may limit the increase of its performance.

3 Main Positive Features of Smoke Testing:

1. Fast process for figuring out if software operates properly;
2. Well suited for detection crashes;
3. Effective method to verify that many software components are “alive”.

Like any other testing, such as mobile application testing or desktop application testing, smoke testing needs test cases. For this method test cases should be written in order to cover the full-scale range of the critical functional and features of the software. For example, Check if the website launches properly, or Verify if the application is responsive.

If the smoke testing demonstrates that software is poorly developed and the major functional does not work – there is no sense to perform automated testing or manual testing. The developers have to go few steps back and modify as well as improve the basic functions of the product.