It turns out that many testing activities can be performed on a new application build before its detailed verification. Among them are build acceptance testing, smoke testing, sanity testing.
Each testing type concentrates on different issues and has its own goal. But all of them are elaborated in order to discover software bugs as early as possible and increase the efficiency of the testing process.
Sanity testing is a type of regression testing. It is often executed during web site testing, desktop testing and mobile application testing. Its aim is to make sure that little additions in the code and correction of the errors that relate to certain functionality operate as intended. Sanity testing is executed before other testing types such as functional testing, performance testing and so on.
Peculiarities of Sanity Testing Are:
- It deeply examines certain functionality of the application, determines whether the improvements and error corrections didn’t break anything in the related area.
- As a rule, it is manual testing; this type of testing is unsuitable for automation.
- It is executed in order to make sure that certain functions work in compliance with the specification requirements.
- It is a kind of acceptance testing; it determines whether the build with new additions and corrections is good for further verification.