Prerequisite – Software Testing
1. Sanity Testing :
Sanity Testing refers to analyze/test the software after modification. It is a part of Regression Testing, where the Regression Testing focuses on a wide variety of area of the application, there Sanity Testing focuses only on certain functionalities. It examines the product quality and its readiness for further tests.
Sanity Testing checks the software product after addition/changes of some functionalities. This testing is usually performed after receiving a fairly stable software build.
2. Regression Testing :
Regression Testing refers to analyze/test deeply to all the functionalities of the software product/system after any changes in code, bug fixes, modification, update in functionality etc. It checks and confirms that the recent changes in the software product has no adverse effects on the other functionalities of the software product.
Regression Testing is the complete testing of the functionalities which is performed after checking certain functionalities by Sanity Testing. This testing is performed on stable builds.
Difference between Sanity Testing and Regression Testing :
|S.No.||Sanity Testing||Regression Testing|
|01.||Sanity Testing is performed to check the stability of new functionality or code changes in the existing build.||Regression testing is performed to check the stability of all areas impacted by any functionality change or code change.|
|02.||Sanity Testing is part of Regression Testing.||Regression Testing is independent testing.|
|03.||It is executed before Regression Testing and after Smoke Testing.||It is executed based on the project and availability of resources, manpower and time.|
|04.||Sanity Testing is considered as a Surface Level Testing.||Regression Testing is not considered as a Surface Level Testing.|
|05.||It examines few functionality of the software.||It examines extended mostly all functionality of the software.|
|06.||Sanity Testing does not use scripts.||Regression Testing uses Scripts.|
|07||Sanity Testing is often carried out manually.||Regression Testing is often preferred to continue with automation.|
|08||Performing Sanity Testing increases the product cost/budget cost.||Performing Regression Testing increases the product cost/budget cost.|
|09||Complete test cases are not executed in the product during this Sanity Testing.||Complete test cases are executed in the product during this Regression Testing.|
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Difference between Re-Testing and Sanity Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Sanity Testing | Software Testing
- Difference between Smoke Testing and Regression Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Software Engineering | Regression Testing
- Why your Regression Testing is taking you longer than necessary
- Difference between Correlation and Regression
- Difference between Frontend Testing and Backend Testing
- Difference between Black Box Testing and Gray Box Testing
- Difference between Unit Testing and Integration Testing
- Difference between System Testing and Acceptance Testing
- Difference between Performance Testing and Load Testing
- Difference between Unit Testing and Sandwich Testing
- Difference between Unit Testing and System Testing
- Difference between Load Testing and Stress Testing
- Difference between Stress Testing and Volume Testing
- Difference between Volume Testing and Load Testing
- Difference between Agile Testing and Waterfall Testing
- Difference between Active Testing and Passive Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.