Sanity Testing | Software Testing

Regression testing has a subset called sanity testing. Sanity testing is carried out to verify that the code changes are functioning as intended. In order to determine whether testing for the build can continue or not, sanity testing is a pause. While conducting sanity testing, the team's main objective is to confirm that the application is functional rather than conducting in-depth analysis. 

Sanity testing is typically done on builds when an immediate production deployment, such as a critical bug fix, is necessary. The goal is to show that the software's developer was rational (and sane) in how they created it, not to thoroughly test the new functionality. Suppose, for instance, that your scientific calculator output is 2 + 2 = 5. Tests of more complex features, such as sin30 + cos 45, are rendered useless.