Why Do We Perform a Smoke Test?

Why Do We Perform a Smoke Test?

After the new functionality is ready, it is added to the test site and then to the production site. The process of adding new functionality into another environment is carried together with testers. After you are done with this work, be sure to check the following:


  • Open the main pages of the application, search / create objects in them.
  • Check that there are no problems fixed during the previous addition of the functionality.


Run a smoke test. Smoke test is a quick check of the main functionality. Typically, it is executed after the new code is added to a website. You need to start running this test on the part of the site that is available to end users. For example, you are testing an online store that consists of 2 parts. The first part is available for buyers. It consists of a catalog of goods, a basket and the order page. The second part is available for administrators and managers who process purchase orders. In this case, testing should begin with the first part, since it is available to more users and its idle state costs the business dearly. Conducting a smoke test for the online store, you need to check that all product categories are browsed, items are added to the shopping cart and the contents of the cart are easily viewed. You also need to complete the order. During the Smoke test, you do not need to pay attention to detail and check infrequent cases. Its purpose is to make sure that the main functionality works as intended and to identify the most critical bugs.


Beta testing services are necessary to verify pre-release software products in real-world environment. The product’s users or their representatives are assigned to do this job to see how they interact with the item under test and what they are dissatisfied with.


Check the fixes made to this site to make sure that the bugs have not occurred again. It happens that when a website is deployed on the production environment and is under heavy load, new bugs that were missed during the testing phase reappear. It is not always possible to fix them directly on a food site therefore temporary solutions to the problem are found. Then the correct fix is made in the test environment, checked and then planned to be uploaded to the product website. Unfortunately, some such pitfalls are forgotten and eliminated only during the upload process. Consequently, you should always record all the situations relating to any interferences with the operation of the product site and check that nothing has changed on the web resource, namely the old bug fixes have been sitting on it after the new features have been added to it.

Leave a Reply

Your email address will not be published. Required fields are marked *