Database Testing Test Cases

Database Testing Test Cases Example:

We will write some basic tests that must be performed on a database. As a tester, you need to validate the below test:

Database Testing Scenario

• Check if correct data is getting saved in the database upon successful page submit for Database Testing
• Check values for columns which are not accepting null values
• Check for data integrity. Data should be stored in single or multiple tables based on design
• Index names should be given as per the standards, e.g. IND_<Tablename>_<ColumnName>
• Tables should have a primary key column
• Table columns should have description information available (except for audit columns like created date, created by, etc.)
• For every database add/update operation log should be added
• Required table indexes should be created
• Check if data is committed to the database only when the operation is completed
• Data should be rolled back in case of failed transactions
• 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)
• Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)
• Stored procedures should not be named with prefix “sp_.”
• Check values for table audit columns (like created date, created by, updated date, updated by, isdeleted, deleteddate, deletedby, etc.) are populated properly
• Check if input data is not truncated while saving. Field length shown to the user on a page and in database schema should be the same
• Check numeric fields with minimum, maximum, and float values
• Check numeric fields with negative values (for both acceptance and non-acceptance)
• Check if radio button and dropdown list options are saved correctly in the database
• Check if database fields are designed with the correct data type and data length
• Check if all table constraints like a Primary key, Foreign key, etc. are implemented correctly
• Test stored procedures and triggers with sample input data
• Input field leading and trailing spaces should be truncated before committing data to the database
• Null values should not be allowed for the Primary key column
• Verify that data inserted from UI is reflecting properly in the appropriate table.

If you found any missed test cases, then feel free to drop the test case in the comment section so that it will help us to give quality content, and also it helps the testers.