Software Testing – Smoke Testing Vs Sanity Testing
To deliver high-Quality Software Application to end users, every Software Development Company perform iterative testing on Software Applications. After, every code change Software Application goes through Smoke Testing to ensure the application’s base features are working as per expectations. Once the Smoke Testing is passed then Software Testing teams start Sanity tests which are much focused on impacted areas where the latest code change happened.
Smoke Testing:
Smoke Testing is the type of Software testing that guarantees an application’s basic and critical features are working fine. In other words, we can say that smoke testing is used to perform to test all the functionalities of the software application. Smoke Testing confirms stability of build. Smoke Testing is the Software Testing team responsibility by manual and automation tools.
Some Popular Automation Tools are :
- Selenium
- Cypress
- Katalon Studio
- Pytest
- HP UFT
Sample Smoke Test Cases: Suppose we have mobile application for flight booking
- Launch Flight Booking Application and verify splash images and landing screen
- Verify non logged user can search flights
- Verify non logged user can chose flight, check price and application redirect for login when user proceed for booking
- Verify logged in user can search flight and book flight
- Validate invoices for Booked flights and notifications
Sanity Testing:
Sanity Testing is the type Software Testing which performed within specific module. It is detailed in nature ensure new code changes working correctly. Sanity Testing can be consider as regression testing which performs within module. Sanity Testing execution is the Software Testing team responsibility. It is less documentative in nature.
Sample Sanity Test Cases : Suppose we have flight booking application and some code changes happens in Calendar module. So below test cases can be consider for Sanity Test Cases.
- User should able to select date and book flight on current date or future
- Application should not allow user to book flight in backdate
- User should book flight for round trip as well
- App can not allow user to book flight without date selection
- Verify number of days in various months February (leap and non leap year) and other months
Difference between Smoke Testing and Sanity Testing
| Smoke Testing | Sanity Testing |
|---|---|
| Objective of Smoke Testing is to confirm that new build is stable enough to perform regression testing. In this testing we cover basic functionality of Application | Objective of Sanity Testing is to ensure that bugs are fixed and working as expected. Sanity testing is usually perform within module |
| Smoke Testing is considered as narrow UAT Testing. | Sanity Testing is considered as narrow regression testing which is performed within module |
| Smoke Testing performed by Manual and Automation as welll. | In general Sanity Testing is manual as its done for new feature or code change. |
| Smoke Testing is performed first and its just to check build stablity. | Sanity Testing is performed on Stable build or we can say after completion of Smoke Testing |
| Smoke Testing is well documented. | Sanity Testing is not documented |
ThoughtCoders is specialized Software Testing Company which provides vast range of Quality Assurance, Test Automation, Non Functional Testing and DevOps services. Our experts helps businesses to automate their Smoke Test cases and Regression Test Cases. Feel free to Contact Us on info@thoughtcoders.com if you are looking for any Quality Assurance Services.
To learn more about Quality Assurance Concepts, Test Automation and performance Testing, you may explore our blogs section. We have started summer trainings programs for young engineering graduates as well.
Must Read:
- Top Software Testing Company in Australia
- Top 10 Software Testing Companies in Canada
- Testing Daily – One Stop Learning Application for Software Testers
