| |
|
Write Down 24 Database Testing Test Scenarios
Question Posted on 08 Feb 2017
Home >> Testing >> Testing Questions >> Write Down 24 Database Testing Test Scenarios |
1. Need to check if correct data is getting saved in database once submiting it
2. Need to check values for columns which not accept null value
3. Need to check data integrity where data should be saved in single or multiple tables asper the design
4. Index names should be given as per the standards e.g. IND_Tablename_ColumnName
5. Tables must have primary key column
6. Table columns should have description information available for some scenrio it is avoid for some column like for created date and created by etc.
7. There must be log For every database add and update operation
8. Must have the Required table indexes should be created
9. Need to check data is committed to database only when the operation is successfully completed
10. Must have applied commit and rollback function so that it will helps in case of failed transactions
11. Developer must takecare of Database name it should be given as per the application type i.e. test, UAT, live etc.(It is a good practice)
12. Database logical names should be given according to database name (It is a good practice)
13. Stored procedures should not be named with prefix sp becasue this is for system store procedure
14. Need to check values for table audit columns like updatedate, updatedby,createddate, createdby, isdeleted, deleteddate, deletedby etc. are filled properly
15. Need to check the input data is not truncated while saving.
16. Need to check numeric fields with minimum, maximum, and float values
17. Need to check numeric fields with negative values in both acceptance and non-acceptance
18. Need to Check if radio button and dropdown list options are saved correctly in database
19. Need to check the database fields are designed with correct data type and data length
20. Need to check if all table constraints like Primary key, Foreign key implemented correctly
21. Need to check the stored procedures and triggers with sample input data
22. Need to check input field leading and trailing spaces should be truncated before committing data to database
23. Need to check the null values should not be allowed for Primary key column
24. Need to check field length shown to user on page and in database schema should be same | |
|
|
|
|