Sanity Testing - (Other types of Testing)

Sanity testing is a type of software testing that is performed after a major change has been made to the software to ensure that the new feature or updates have not adversely affected the existing software functionality. In this tutorial, we'll discuss what sanity testing is and when it should be used.

Syntax

There is no specific syntax for writing and conducting sanity tests, as it's more about the overall testing process.

Example

Suppose that you have made a major change to your web application that includes redesigning the homepage and updating the checkout process. To ensure that the changes have not affected the basic functionality of the web application, you can perform a sanity test that includes simple tasks such as:

1. Checking that the homepage loads and displays correctly
2. Navigating to other pages in the web application to ensure that links are working correctly
3. Testing the checkout process to ensure that products can be added to the cart, that the cart can be checked out correctly, and that payment is successful.

Explanation

Sanity testing is a quick and simple test on the updated software to ensure that the updates have not introduced any major issues. It is not an exhaustive test, but rather a quick and efficient one.

The objective of sanity testing is to determine whether it is reasonable to proceed with the testing process or whether further testing is required. If issues are found, further testing is needed before the software can be released.

Use

Sanity testing can be used when:

• There is a major update or change to the software
• It's necessary to check that the basic functionality of software is still working as expected
• There is a limited time or budget available for testing

Important Points

Here are some important points to keep in mind when conducting sanity testing:

• It is not a substitute for other types of testing such as functionality or performance testing.
• It is a quick test that can be done within a limited time and budget.
• It is a basic minimum set of tests used to confirm that the major changes/addition/updates have not broken the existing application's functionality.
• Sanity testing should be performed before extensive testing begins.

Summary

Sanity testing is a simple yet effective way to ensure that a major change or update has not affected the basic functionality of the software application. It is a quick and cost-effective method of ensuring that further testing can proceed or identify whether additional testing is required. It is not a substitute for thorough testing, but it is a valuable addition to the testing process.