Sanity Testing Checklist For a software build

“Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous.” – James Bach

Sanity Testing is the most commonly confused term in the field of Software testing. This article addresses the basic sanity testing checklist that helps you to feel confident that you haven’t missed any important aspect while doing a sanity check on your application.

By definition, Sanity Testing is performed wherein the aim is to verify if the new functionality, change, or fix is working and has not affected the existing functionalities.

To cut a long story short, sanity testing is a quick, broad, and shallow testing that is done to determine whether the application is reasonable to proceed with further testing.

How to do Sanity Testing?

Over other types of software testing, the main objective of sanity testing is to verify and validate the newly implemented features and that new features have not affected the functionality of the existing features in the application and also check the features that are associated with the new features. If this Sanity test fails, the Testing team need not proceed with further rigorous testing and can quickly send back the release to the developers for fixing the bugs. If the Sanity test passes, the release can proceed with further thorough testing.Here is a basic checklist that needs to be taken into account while doing a Sanity check for a software build.

UI Testing

User Interface Testing is to basically check the look & feel of the application. This includes,

1. Check if font size/style/color is used as per the requirement
2. Check for spelling and grammatical errors all over the website
3. Check the alignment of texts, images, icons, buttons, etc are correct
4. Check if breadcrumbs are displayed
5. Check for mega menus
6. Check for broken images and the image quality
7. Check for Zoom in, Zoom out for Product images
8. Check if the images don’t have any watermark
9. Check if all the web elements are displayed correctly in all screen resolutions, browsers, and different platforms
10. Check if scroll bars are visible wherever necessary
11. Check if the links are distinguishable from normal text
12. Check if error/warning/success messages are displayed correctly and distinguishable based on the color
13. Check if the text field accepts characters or as based on the requirement
14. Check if the autocomplete function is working correctly for a text field
15. Check if a mandatory text field is identified by a * sign
16. Check if the element focus is working
17. Check if the tooltip is displayed correctly

Functional testing

The purpose of functional tests is to verify all features are functioning as per the requirement. This includes,

1. Check field validations
2. Check if a form is submitted after entering data from all the fields
3. Check if documents such as PDF, DOC, XLXS are downloadable in different browsers and OS
4. Check the search functionality
5. Check sorting, filtering, and pagination functionality
6. Check if the Product is added to the cart by clicking Add to Cart
7. Check by adding multiple items to the cart
8. Check if the Product price is displayed correctly in the cart
9. Check by deleting/updating the product from PLP, PDP, Mini Cart, Shopping cart
10. Check for Login functionality from the Login page, Cart page, and Checkout page
11. Check the Create account functionality
12. Check My Account module wherein the user is able to edit/update account information
13. Check Forgot Password functionality
14. Check Logout functionality
15. Check Payment methods
16. Check Tax Calculation
17. Check Discount code functionality
18. Check if the order is placed successfully
19. Check for a confirmation message after placing an order
20. Check Order processing.

Integration Testing

1. Check for broken links
2. Check if the social networking icons navigate to respective pages
3. Check if the Logo is a clickable link and navigates to Home Page

To sum up, the above-mentioned checklist provides a quick evaluation of the quality of the software and in turn saves a lot of time and effort a tester puts in to make a decision beforehand whether to proceed with rigorous testing or give back the build to the developers. I hope this article is useful. Happy Testing!!