Smoke VS Sanity

Differences between Smoke Testing and Sanity Testing:

Aspect	Smoke Testing	Sanity Testing
Purpose	Verifies major and critical functionalities to ensure basic stability.	Focuses on specific functionalities or areas to ensure changes haven't adversely affected them.
Scope	Covers a broad spectrum of functionalities, providing a quick assessment.	Targets specific areas or functionalities that have undergone recent changes.
Depth	Generally shallow, checking critical paths without in-depth testing.	More detailed and specific, diving deeper into particular functionalities.
Timing	Performed after a new build or release to ensure basic functionality.	Typically performed during later stages of the development cycle after specific changes.
Frequency	Generally performed whenever a new build is available.	Conducted as needed, specifically after changes or fixes.
Execution Criteria	Has a predefined set of test cases covering essential functionalities.	Test cases selected based on specific changes or features implemented.
Documentation	Often has a standard set of documented smoke test cases.	Documentation may vary based on the changes made, covering specific modifications.
Comprehensive Testing	Not exhaustive, providing a quick and general check.	More thorough in the areas it covers, ensuring stability in specific functionalities.
Regression Testing	May include some regression testing but is more focused on identifying showstopper issues.	Often includes regression testing for modified functionalities to ensure existing features are not negatively impacted.
Automation	Can be automated for quick and repetitive execution.	Automation can be beneficial, especially for frequent changes in specific areas.
Relationship with Other Testing Phases	Serves as a prerequisite for more comprehensive testing phases. If it fails, further testing may be halted.	Typically follows smoke testing and occurs after specific changes, ensuring targeted modifications integrate well.