This is a method of testing that focuses on the most critical tests in order to determine if the application can be subject to further testing. This is also known build verification testing.
Example
Let's look at an example to help us understand. Let's say we have a large web app to test and thousands of test cases. If we are given a build that contains a new feature or has some bugs fixed, testing could be done by starting the entire test execution cycle. It will take a lot of time and resources to complete the test execution cycle.
If the build is stable and has no major issues, it's all fine. The problem is when the build is unstable and core functionality does not work. This case has resulted in wasted testing time, as well as a delay for the development team and stakeholders regarding stability.
Smoke testing was created to handle such cases. This approach allows us to start with only the core functionalities and not the entire regression testing cycle.
This allows us to quickly switch to extensive testing if the build is stable. If it is not stable, we notify the development team immediately.
Test cases that are extremely critical to an app, such as Gmail, can be included in smoke tests. The user must be able log in to the application. Inbox should contain all received emails. Users should also be able to compose and send mail.
Benefits of smoking testing
· It allows you to quickly identify issues that affect the critical functionality.
· Smoke tests can save a lot of time, as the build is rejected. The testing team also doesn't have to execute all the test procedures in the affected build.
· Smoke testing can quickly identify integration issues
The testing of electrical appliances gave rise to smoke testing. To test an electrical device, you had to first plug it into a power outlet to see if it produces smoke. If the smoke is absent, it indicates that the electrical circuits have not failed and can be tested for functionality.
Comentarios