Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.
The Goal of Sanity Testing is to check that the software should meet the client expectation. Sanity Testing is very cost effective. if Sanity Test fail then revert the build to the developer team which save lots of time.
The Objective of Sanity Testing is not to verify thoroughly the new functionality of the software.
Sanity Testing always perform when the software PASS in the Smoke Testing. Sanity Testing is the narrow regression testing which focus on new area of the software. Sanity Testing is narrow and deep.
Sanity testing perform after lots of regression testing is already performed and come now for minor changes in build. In this cases we perform the deep testing of functionality for these changes. Sanity testing is the Sub Regression Testing.
The Goal of Sanity Testing is to check that the software should meet the client expectation. Sanity Testing is very cost effective. if Sanity Test fail then revert the build to the developer team which save lots of time.
The Objective of Sanity Testing is not to verify thoroughly the new functionality of the software.
Sanity Testing always perform when the software PASS in the Smoke Testing. Sanity Testing is the narrow regression testing which focus on new area of the software. Sanity Testing is narrow and deep.
Sanity testing perform after lots of regression testing is already performed and come now for minor changes in build. In this cases we perform the deep testing of functionality for these changes. Sanity testing is the Sub Regression Testing.
Comments
Post a Comment