As you read thoroughly all testing types, now this article is about Sanity Testing and Smoke Testing which are the important testing after application build received. Also the I have mentioned some of difference between Sanity and Smoke testing.
Difference between smoke and sanity testing:
Sanity testing use to a set of tests that confirm a build’s stability and the availability of major components and modules of the product. The tests will be execute for every build used by QA team also the scenario automated are generally execute on a daily basis. Each major new feature defined within the project PRD must be represented by one or more test cases in the Sanity Test.
When the project is driven based on Pass I, Pass II and Pass III where Pass II will be called as comprehensive pass and Pass III will be called as Sanity testing Pass. In the Sanity testing (Final) Pass only the bugs got fixed after the comprehensive pass will be tested and a formal regression testing will be done with respect to the bug fix. Apart from, testing would be performed on the major functionalities of the product to confirm that the final code has not broken any other functionalities which were working before.
Smoke testing use to a set of tests that validate basic functionality across a feature suit. Also referred to as CRUD testing (Create, Read, Update and Delete records), these testing are intended to validate most basic “go-paths” within the code. Smoke tests should cover core or legacy functionality as well new features for the project. Smoke testing generally execute following Sanity Testing and are more thorough in scope.
you will see next another difference between smoke and sanity testing.
When a build is received with build letter in email , a smoke test is run to ascertain if the build is stable and it will be considered for further next testing
Smoke testing can be use for testing the stability of application in any interim build.
Smoke testing can be executed for platform qualification tests.
Once a new build is received with minor revisions, instead of doing a thorough or complete regression testing, a sanity test is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a sub suit of regression testing and a group of test cases are executed which are related to the changes made to the application.
Generally, when the multiple cycles of testing are executed, sanity testing may be done during the later cycles after through regression testing cycles.
Soon I will publish more difference between smoke and sanity testing