Essentially, smoke tests verify stability of the build, while sanity tests concentrate on specific features and defects within the build. Because smoke tests verify the entire application at a high level, they are often seen as a part of acceptance testing.

1. SANITY TESTING AND SMOKE TESTING
Presented By: Group-6
Sajid Ferdous-19511058
Mohammad Ahnaf Tahmeed- 19511086

2. WHAT IS SANITY TESTING ?
 Sanity Testing is a subset of regression
testing. Sanity testing is performed to ensure
that the code changes that are made are
working as properly. Sanity testing is a
stoppage to check whether testing for the build
can proceed or not.
 The focus of the team during sanity testing
process is to validate the functionality of the
application and not detailed testing. Sanity
testing is generally performed on build where
the production deployment is required
immediately like a critical bug fix.

3. FEATURES OF SANITY TESTING
 Subset of Regression Testing:
Sanity testing is a subset of regression testing and focuses on the smaller section of the
application.
 Unscripted:
Most of the times sanity testing is not scripted.
 Not documented:
Usually sanity testing is undocumented.
 Narrow and deep:
Sanity testing is narrow and deep approach of testing where limited functionalities are covered
deeply.
 Performed by testers:
Sanity testing is normally performed by testers.

4. ADVANTAGES OF SANITY TESTING
● It helps us to find any deployment or compilation
issues.
● It is less expensive as compared to other types of
software testing.
● It helps in rapidly finding the bugs in the core
functionality.
● There is no documentation mandatory for sanity
testing, that's why it can be executed in lesser time.

5. DISADVANTAGES OF SANITY TESTING
● It's become a very complex process for the developers to understand how to
fix the defects acknowledged throughout the sanity testing if they do not
follow the design structure level.
● All the test cases are not covered under sanity testing.
● It is emphasized only on the statement and functions of the application.
● We do not have future references since the sanity testing is unscripted.

6. WHAT IS SMOKE TESTING
 Smoke Testing is a software testing method that
determines whether the employed build is stable or
not. It acts as a confirmation of whether the quality
assurance team can proceed with further testing.
 Smoke tests are a minimum set of tests run on each
build. Smoke testing is a process where the
software build is deployed to a quality assurance
environment and is verified to ensure the stability
of the application. Smoke Testing is also known as
Confidence Testing or Build Verification
Testing.

7. CHARACTERISTICS OF SMOKE TESTING
 Smoke testing is documented.
 Smoke testing may be stable as well as unstable.
 Smoke testing is scripted.
 Smoke testing is a type of regression testing.
Smoke Testing is usually carried out by quality assurance
engineers.

8. TYPES OF SMOKE TESTING
 Manual Testing: In this, the tester has to write, develop, modify or update the
test cases for each built product. Either the tester has to write test scripts for
existing features or new features.
 Automated Testing: In this, the tool will handle the testing process by itself
providing the relevant tests. It is very helpful when the project should be
completed in a limited time.
 Hybrid Testing: As the name implies, it is the combination of both manual and
automated testing. Here, the tester has to write test cases by himself and he can
also automate the tests using the tool. It increases the performance of the testing
as it combines both manual checking and tool.

9. SMOKE TESTING VS SANITY TESTING KEY FEATURES