Smoke Testing vs. Sanity Testing
?? Smoke Testing vs. Sanity Testing
Smoke Testing - A broad, high-level check to ensure critical functionalities work. - Performed after a new build is deployed. - Helps decide if the build is stable enough for further testing. - Covers all major features but does not go deep. - If it fails, the build is rejected for further testing. - Quick execution, often automated.
Sanity Testing - A focused, narrow test to verify specific bug fixes or changes. - Performed after minor changes, patches, or bug fixes. - Ensures that fixes didn’t introduce new issues. - Tests only the affected modules, not the entire application. - If it fails, deeper testing is stopped until fixes are made. - Slightly more detailed than smoke testing.
? When to Use? -
Smoke Test → When a new build is received.
Sanity Test → When a bug fix or minor update is applied.