When Smoke Testing is performed?

[william]

When Smoke Testing is performed? How it can be performed? Is it easy or tough?

[Nick]

<span style=”color: #454545; font-family: Roboto;”>Smoke testing is a type of preliminary testing that is used to test whether the product is stable or not. It is a subcategory of test cases that aims to assess the main functions of software application.</span>

[Jahnvi]

Smoke testing, also known as “build verification testing”, is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions to work. The result of this testing is used to decide if a build is stable enough to proceed with further testing.

It can also be used to decide whether to announce a production release or a revert. The term “smoke testing”, it is said, came to software testing from a similar type of hardware testing, in which the device passed the test if it did not catch fire(or smoke)the first time it was turned on.

ASP.Net Software Development

[ashwini]

<p style=”margin-bottom: 1.25em; margin-left: 0;”>Smoke testing is performed during the early stages of software testing to quickly assess whether the critical functionalities of the application are working as expected. The primary goal of smoke testing is to determine if the application is stable enough for more in-depth testing.</p>
<p style=”margin-bottom: 1.25em; margin-left: 0;”>Smoke testing is typically conducted after the completion of a development build and before more comprehensive testing, such as regression testing or functional testing, takes place. It serves as a preliminary check to catch major defects or issues before investing time in further testing. If the application fails the smoke test, it indicates that there are critical problems that need to be fixed before proceeding with more extensive testing.</p>
<p style=”margin-bottom: 1.25em; margin-left: 0;”>The term “smoke testing” originates from electronic hardware testing, where engineers would turn on a piece of hardware and check for any physical smoke or signs of fire, which would indicate a severe problem with the hardware.</p>
<p style=”margin-bottom: 1.25em; margin-left: 0;”>In software testing, smoke testing involves running a basic set of tests to verify essential functionalities of the application. This could include:</p>

1. Verifying that the application launches without any critical errors.
2. Checking basic navigation and functionality within the application.
3. Testing crucial features that are critical to the application’s core purpose.
4. Ensuring that important interfaces or integrations are working.

<p style=”margin-bottom: 0; margin-left: 0;”>Once the application passes the smoke test, it is considered stable enough to proceed with more comprehensive testing. If the application fails the smoke test, it is sent back to the development team for necessary fixes, and smoke testing is repeated once the issues are resolved.</p>

[Author]

Posts