Smoke and sanity testing are considered to be the two important testing types focused on making sure that the code’s basic functionality is working as per the expected requirements. Though both these testing types have different approaches towards testing, but, the goal is to make sure that eventually a quality product is being built.
Both these testing methods can be done manually or can be automated based on the project scope and business specific requirements. In this article, you will get to know what are the differences between smoke testing and sanity testing.
It is a testing method that verifies whether a deployed software build is stable or not. The QA team gets a sort of confirmation so that they can proceed to further levels of testing. Early major issues or defects in the software development process are identified by this testing method. Smoke testing is designed to demonstrate conformance to requirements and system stability. It is also known as “Build Verification testing.”
Example:
A user is using a Facebook application. It’s quite natural that new feature updates are being added internally. But, the actual user will not get affected in terms of using the application, though the internal changes have taken place and the new feature updates have been added successfully. This means that an application is being properly used by the user.
What is Sanity testing?
Once the software build is received, sanity testing is performed to make sure that the code changes that have been introduced are working as per the required expectations. It acts as a checkpoint to ascertain whether the testing for the build can proceed further or not. If the sanity test fails, then the testing team rejects the build thus saving both time and money. It is performed only after the build passes the smoke test and the necessary assurance is provided by the QA team.
Example:
In an e-commerce project, the login page is one of the main modules. The login page has been identified with a defect. Less than four alpha numeric characters are accepted by the password field, but, the requirements clearly state that the password should not be below eight characters.
The testing team reports the defect to the development team so that they can resolve it. The development team does the needful and sends it back to the testing team for clearance. The testing team verifies the changes that have been made are as per the requirements or not. It also checks whether the changes that have been made will have an impact on other functionalities.
Now the password functionality needs to be updated on the user profile page. This is done to validate both the login page and user profile and make sure that the password related checks are working in exact accordance on both the pages.
Difference between Smoke testing and Sanity testing:
Conclusion: If you are looking forward to implementing smoke testing or sanity testing or both for your specific project, then do get connected with a globally renowned software testing services company that will provide you with a feasible testing strategy that is in line with your project specific requirements.
About the author: I am a technical content writer focused on writing technology specific articles. I strive to provide well-researched information on the leading market savvy technologies.
Comments