Software sanity tests are synonymous with smoke tests. A sanity or smoke test determines whether it is possible and reasonable to continue Software Testing. It exercises the smallest subset of application functions needed to determine whether the systems are accessible and the application logic is responsive.
During sanity testing the below mentioned checklist is almost applicable for all types of web applications depending on the business requirements.
a) UI Testing:
1. Web page title as per the page’s functionality.
2. Spelling/grammatical mistake (e.g. Text, Caption, Label).
3. Proper field alignment (Left margin, right margin, bottom margin, top margin).
4. Same font size/style or as per the requirement.
5. Proper space between texts, text lines, fields.
6. Standard format and size of button.
7. Textbox: Border, alignment, size, length, Data Type.
8. Combo box: Size, alignment, showing valid value.
9. Date picker (Not by keyboard, from date to date range).
10. Mandatory field identified with an identification like (*) sign.
11. Image length, size, alignment
b) Functional Testing:
1. Mandatory and composite field validation.
2. Error message not mandatory for optional field.
3. Numeric field does not accept the alpha numeric and proper error message display.
4. Max length checking for specific input field (e.g. Credit card number, Account number).
5. Confirmation message for Insert/update/delete operations.
6. Correct format of amount value.(Should be numeric)
7. Uploaded documents are opened and generated properly.
8. Validation (different fields….Equivalence partitioning/Boundary value analysis/Positive testing/Negative/Page Refreshing testing).
9. System works properly with multiple browsers.
10. Pagination works and number shows properly.
c) Database Testing:
1. Database name, Tables, columns name, column types matches according to requirement.
2. Data saves properly into the database after the each page submission.
3. Data display on the front end and make sure it is same in the back end.
4. Is any difference between Live and Test environment (Database Name, Table Name, Column Name, Data Type, Entity Relationship Key – Primary, Foreign, Unique key)
5. Checking Procedure/Function Create/Update related information(Entity Name, Author, Create/Update Date, Description/Purpose)
d) Security Testing:
1. Session timeout checking. Whether the page is expiring after the specific time.
2. Does the page browse if I paste it in a newly open browser?
3. Browser back-forward button checking if the page consist any calculation or information submission. Does the browser’s back-forward button re-submit the page?
4. Does this application has admin/user log in the database? (IP Address, user ID, Login/logout date and time) .
5. Password, Account number, credit card number display in encrypted format.
6. Access the secured web page directly without login.
7. User account gets locked out if the user is entering the wrong password several times.
(If available in BRS/SRS).
Above all these testing you can easily learn from different kind of international training. Like, ISTQB or International Software Testing Qualification Board.