Scribd
Upload
78 views12 pages

Smoke Testing and Sanity Testing

Smoke testing verifies that critical functionalities work as expected after a new build. It is quick and meant to check stability before detailed testing. Sanity testing checks that minor code changes or bug fixes did not introduce new issues, by testing major functionality at a high level rather than thoroughly. Smoke testing evaluates the whole system while sanity focuses on particular components. Both aim to quickly reject broken builds early to save testing time and costs.

Uploaded by

Mausam Rana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
78 views12 pages

Smoke Testing and Sanity Testing

Smoke testing verifies that critical functionalities work as expected after a new build. It is quick and meant to check stability before detailed testing. Sanity testing checks that minor code changes or bug fixes did not introduce new issues, by testing major functionality at a high level rather than thoroughly. Smoke testing evaluates the whole system while sanity focuses on particular components. Both aim to quickly reject broken builds early to save testing time and costs.

Uploaded by

Mausam Rana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Smoke Testing and Sanity

Testing
Smoke Testing
• Software testing technique performed post software build to verify
that the critical functionalities of software are working fine.
• It is executed before any detailed functional or regression tests are
executed.
• Smoke testing is the initial testing process exercised to check whether
the software under test is ready/stable for further testing.
• The main purpose of smoke testing is to reject a software application
with defects so that QA team does not waste time testing broken
software application.
•  The objective is not to perform exhaustive testing, but to verify that
the critical functionalities of the system are working fine.
• It checks whether the deployed build is stable or not as to confirm if
the QA team can proceed with further testing.
When do we perform 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.
Example
• Considering a scenario such as validating the login credentials. Here,
the login functionality of the application has to ensure that only a
registered user is allowed to log in with a valid username and
password. 
• Now, the steps required to perform the test are launching the
application, navigating to the login page, enter a valid username and
password, and then clicking on the login button.
• Now, if the logins are correct, then the actual result will be as
expected, i.e, will be login is successful, or else the status of the test is
declared as fail.
Sanity Testing
• Software Testing performed after receiving a software build, with
minor changes in code, or functionality, to ascertain that the bugs
have been fixed and no further issues are introduced due to these
changes.
• The goal is to determine that the proposed functionality works
roughly as expected.
• If sanity test fails, the build is rejected to save the time and costs
involved in a more rigorous testing.
• The objective is "not" to verify thoroughly the new functionality but
to determine that the developer has applied some rationality (sanity)
while producing the software.
• For instance, if your scientific calculator gives the result of 2 + 2 =5
Then, there is no point testing the advanced functionalities like sin 30
+ cos 50.
When do we perform Sanity Testing?
• Sanity testing is performed after the build has clear the Smoke test
and has been accepted by QA team for further testing, sanity testing
checks the major functionality with finer details.
• Sanity testing is performed when development team needs to know
quick state of the product after they have done changes in the code
or there is some controlled code change in a feature to fix any critical
issue
Example
• Consider a project, where there are five modules such as home page,
login page, new user creation, user detail page, and task creation. As
per the requirements, the username in the login page should not
accept less than six characters, and the bug is created when a
username with less than six characters is accepted.
• The bug is then reported to the development team for fixing by the
testing team. Now, the development team fixes the issue and again
passes it on to the testing team to re-check. The testing teams then
check that the bug fixed by the development team is not affecting the
functionality of other modules. This way of testing the extreme
functionalities of the modules and not going in detail is nothing but
sanity testing.
Smoke Testing Sanity Testing
Smoke Testing is performed to ascertain that the critical Sanity Testing is done to check the new functionality/bugs
functionalities of the program is working fine have been fixed

The objective of this testing is to verify the "stability" of The objective of the testing is to verify the "rationality" of
the system in order to proceed with more rigorous testing the system in order to proceed with more rigorous testing

This testing is performed by the developers or testers Sanity testing in software testing is usually performed by
testers

Smoke testing is usually documented or scripted Sanity testing is usually not documented and is unscripted

Smoke testing is a subset of Acceptance testing Sanity testing is a subset of Regression Testing

Smoke testing exercises the entire system from end to Sanity testing exercises only the particular component of
end the entire system

Smoke testing is like General Health Check Up Sanity Testing is like specialized health check up
धन्यवाद

You might also like