Where we learn technology

Database Testing Test Cases – By Naveen AutomationLabs

Database Testing Test Cases 

1. Check if correct data is getting saved in database upon successful page submit

2. Check values for columns which are not accepting null values

3. Check for data integrity. Data should be stored in single or multiple tables based on design

4. Index names should be given as per the standards e.g. IND_<Tablename>_<ColumnName>

5. Tables should have primary key column

6. Table columns should have description information available (except for audit columns like created date, created by etc.)

7. For every database add/update operation log should be added

8. Required table indexes should be created

9. Check if data is committed to database only when the operation is successfully completed

10. Data should be rolled back in case of failed transactions

11. Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)

12. Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)

13. Stored procedures should not be named with prefix “sp_”

14. Check is values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly

15. Check if input data is not truncated while saving. Field length shown to user on page and in database schema should be same

16. Check numeric fields with minimum, maximum, and float values

17. Check numeric fields with negative values (for both acceptance and non-acceptance)

18. Check if radio button and dropdown list options are saved correctly in database

19. Check if database fields are designed with correct data type and data length

20. Check if all table constraints like Primary key, Foreign key etc. are implemented correctly

21. Test stored procedures and triggers with sample input data

22. Input field leading and trailing spaces should be truncated before committing data to database

23. Null values should not be allowed for Primary key column

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation:


Follow me on my Facebook Page:

Let’s join our Automation community for some amazing knowledge sharing and group discussion:


Please follow and like us:


  1. Unknown

    Wonderful post Naveen.could you please create one for performance testing/Accessibility testing as well..

  2. sriram

    It's interesting that many of the bloggers to helped clarify a few things for me as well as giving.Most of ideas can be nice content.The people to give them a good shake to get your point and across the command.

    software testing course in chennai

  3. Unknown

    Good Post! Thank you so much for sharing this pretty post, it was so good to read and useful to improve my knowledge as updated one, keep blogging.

    Python Training in electronic city

    DataScience with Python Training in electronic city

    AWS Training in electronic city

    Big Data Hadoop Training in electronic city

    Devops Training in electronic city

  4. Anaya Shaikh

    When the database of a company is controlled via the internet, this measure is at its best use. There will be a list of users that are authorized to access the data on the database and when this access is restricted, the data is all the more secured. Database Diagram Tool

Leave a Reply

Your email address will not be published. Required fields are marked *