**

What Is the Difference Between Smoke Testing and Sanity Testing in Functional Testing?

**

In functional testing, the difference between smoke testing and sanity testing lies in their objectives and scopes.

**Smoke Testing:**
- **Focus Keyword: Smoke Testing**
- **Definition:** Smoke testing, also known as build verification testing, is a preliminary round of testing that determines whether the most critical functionalities of the software are working as expected.
- **Purpose:** The primary objective of smoke testing is to check if the software build is stable enough for further, more rigorous testing. It helps identify major issues early in the testing process.
- **Scope:** It involves a broad and shallow test of the system and focuses on ensuring that the core functionalities are operational.

**Sanity Testing:**
- **Focus Keyword: Sanity Testing**
- **Definition:** Sanity testing is a more focused and narrow approach to testing that is performed on areas of the software application where changes have been made.
- **Purpose:** The main purpose of sanity testing is to verify that specific functionality or changes have been successfully implemented without affecting the existing functionalities.
- **Scope:** It is targeted towards specific areas of the software to ensure that the recent modifications have not introduced any issues and that the software is still stable.

In summary, while smoke testing checks the basic functionalities to determine the stability of the software build, sanity testing verifies specific changes or additions in a more focused manner to ensure the overall integrity of the software. Both types of testing play crucial roles in ensuring the quality and reliability of the software product.