0% found this document useful (0 votes)
1 views

Smoke Testing

Smoke testing is a software testing process that verifies the stability of a deployed build by checking critical functionalities before proceeding with further testing. It is performed whenever new features are integrated into the existing build and helps identify defects early, reducing costs and risks. The process is essential for ensuring the correctness of the system and improving overall software quality.

Uploaded by

Akhil Suresh
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1 views

Smoke Testing

Smoke testing is a software testing process that verifies the stability of a deployed build by checking critical functionalities before proceeding with further testing. It is performed whenever new features are integrated into the existing build and helps identify defects early, reducing costs and risks. The process is essential for ensuring the correctness of the system and improving overall software quality.

Uploaded by

Akhil Suresh
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

SMOKE TESTING

WHAT IS 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 to run on each build to test software


functionalities.
• Smoke testing is also known as Build Verification Testing or Confidence Testing.

• Smoke test verifies that the important features are working and there are no
showstoppers in the build that is under testing.
WHEN DO WE DO SMOKE TESTING ?

• Smoke testing is done whenever the new functionalities of software are developed and
integrated with existing build that is deployed in QA/staging environment.
• It ensures that all critical functionalities are working correctly or not.
• In this testing method, the development team deploys the build in QA.
• The QA team test the application against the critical functionalities.
• These series of tests are designed to expose the errors in the build. And if these tests are
passed then the QA team continues with functional testing.
• Any failure indicates then the system have to send back to the development team.
• Whenever there is a change in the build , we perform smoke testing to ensure the stability.
EXAMPLES OF SMOKE TESTING

• New registration button is added to the login window and build is


deployed with the new code. So then we perform smoke testing to
ensure the stability of the system.
• Verify that a user can register and log in to an online shopping
platform.
• Verify that a user can browse and search a product catalog.
• Adding item functionality like , able to add item to the cart and the item
should get added to the cart.
• Sign out functionality should be working like, the user should be able to
sign out.
WHAT HAPPENS IF WE DON’T DO SMOKE TESTING

• If we don’t perform smoke testing in early stages, defects may be


encountered in later stages where it can be costly.
• Defects found in the later stages can be show stoppers where it may
affect the release of deliverables.
WHY DO WE DO SMOKE TESTING

• Smoke testing plays an important role in software development as it


ensures the correctness of the system in intial stages.
• Once we complete smoke test then only we can start functional testing.
• All the show stoppers in the build will get identified by performing
smoke testing.
• Smoke testing is done after the build is released to QA. With help of
smoke testing most of the defects are identified at the initial stages of
the development.
• With smoke testing, we simplify the detection and correction of major
defects.
ADVANTAGES OF SMOKE TESTING

• Easy to perform testing.


• Defects will be identified in early stages.
• Improves the quality of the system.
• Reduces the risk.
• Saves test effort and time.
• Easy to detect critical errors and correction of errors.

You might also like