what is Sanity testing?

 Sanity testing is a type of software testing that is performed to ensure that the newly added or modified functionalities or features in the software application are working as expected and do not adversely impact the existing functionalities. It is also known as "smoke testing with a purpose" or "build verification testing."

Sanity testing is performed after the software build is made, and the build has passed the smoke testing stage. The main objective of sanity testing is to verify whether the changes or enhancements in the application are working as intended, and it is safe to proceed with further testing.

Unlike smoke testing, which focuses on testing the basic functionality of the application, sanity testing focuses on testing specific functionalities or modules of the application. The tests performed during sanity testing are more detailed and comprehensive than smoke testing.

Some of the common tests performed during sanity testing include checking the functionality of newly added or modified features, verifying the integration of different modules, verifying the data flow between different components, and ensuring the stability of the application after the changes.

If any issues or defects are found during sanity testing, it is an indication that the changes have impacted the existing functionalities, and the changes need to be rechecked and fixed before proceeding with further testing.

Sanity testing is an important part of the software testing process and helps in ensuring the overall quality and stability of the software application. It is usually performed before regression testing or other types of testing to ensure that the changes made have not impacted the overall functionality of the software.

Examples of Sanity testing

Comments

Popular posts from this blog

What is Smoke testing

java.lang.NoClassDefFoundError: groovy/lang/GroovyObject (issue for Rest Assured project in Eclipse)

Examples of Sanity testing