In software testing, smoke testing (also known as “build verification testing”) is a type of shallow testing that is used to verify that the most important functions of a software build are working correctly. The purpose of smoke testing is to ensure that the build is stable enough to proceed with further testing. In smoke testing we test basic and critical features of the application.

When do we do smoke testing?

Smoke testing is usually done early in the testing process, after the build has been deployed to the test environment. It is generally a quick and lightweight testing method that focuses on the most essential features and functionality of the software. The goal of smoke testing is to identify any major issues with the build as soon as possible, so that they can be addressed before more detailed testing is performed.

We start for each build because we may find Blocker bugs in the next build due to code changes and installation problems.

Smoke testing is usually done manually, but it can also be automated using specialized testing tools. It is an important part of the software testing process because it helps to ensure that the software is of sufficient quality to proceed with further testing, and helps to identify major issues that need to be addressed before the software is released to end users,

Note: Smoke testing should be done whenever the installation takes place to make sure that installation is done properly.

Smoke testing is also called build verification testing. In this we verify if each and every build is testable or not, hence it is also called build verification testing.