smoke test definition code example

Example 1: smoke testing

Smoke Testing is a software testing process that determines whether the deployed software build is stable or not. 
Smoke testing is a confirmation for QA team to proceed with further software testing.
It consists of a minimal set of tests run on each build to test software functionalities. 
Smoke testing is also known as "Build Verification Testing" or “Confidence Testing.”
In simple terms, we are verifying whether the important features are working and there are no showstoppers in the build that is under testing.
It is a mini and rapid regression test of major functionality. It is a simple test that shows the product is ready for testing.
This helps determine if the build is flawed as to make any further testing a waste of time and resources.

Example 2: what is smoke testing

Smoke tests are basic tests that check basic 
functionality of the application. 
They are meant to be quick to execute, and
their goal is to give you the assurance
that the major features of your system 
are working as expected.
• Smoke tests can be useful right after
a new build is made to decide whether or 
not you can run more expensive tests, or
right after a deployment to make sure 
that they application is running properly
in the newly deployed environment.

Example 3: failure rate in smoke test

How often do your smoke test fail?

it does not fail, the rate of fails very very low
not functionality reason
failure rate is very low
%99 due to system issue, network issue.

Example 4: smoke testing

Smoke tests are basic tests that check basic 
functionality of the application. 
They are meant to be quick to execute, and
their goal is to give you the assurance
that the major features of your system 
are working as expected.
• Smoke tests can be useful right after
a new build is made to decide whether or 
not you can run more expensive tests, or
right after a deployment to make sure 
that they application is running properly
in the newly deployed environment.