Database testing
Points:
- Test data integrity
- Test data type
- Test data size
- Test Event driven functionality
- Input item verification
- Test Stored procedure functionality
Points:
- Test data integrity
- Test data type
- Test data size
- Test Event driven functionality
- Input item verification
- Test Stored procedure functionality
Data integrity:
While performing actions on DB, respective changes should be reflected in DB.
- ensure that the available tables are as per design.
- ensure records are getting populated properly in all related tables when inputs are given in the application.
- ensure records are getting deleted in the related tables when the information is deleted in the application (front end).
- verify for modifications of the records.
While performing actions on DB, respective changes should be reflected in DB.
- ensure that the available tables are as per design.
- ensure records are getting populated properly in all related tables when inputs are given in the application.
- ensure records are getting deleted in the related tables when the information is deleted in the application (front end).
- verify for modifications of the records.
*Actions: addition, deletion, updation, insertion
Data Types:
Test the types of entity that are used in database. Entity type should be same as that administrator defined. It is performed on front end as well as from back end also.
Test the types of entity that are used in database. Entity type should be same as that administrator defined. It is performed on front end as well as from back end also.
e.g. Phone: String – administrator, but developer use it as number.
Data Size:
Test the size of entity that is used in database. Entity type should be same as that administrator defined. It is performed on front end by tester as well as from back end during unit testing by developer also.
Test the size of entity that is used in database. Entity type should be same as that administrator defined. It is performed on front end by tester as well as from back end during unit testing by developer also.
e.g. email: max 30 character & min 5 character
Test Event driven functionality:
Event driven actions needs to be tested based on two factors
Events that trigger this action: With developer, QA has to test the event.
Action that performed by above event: testing the SP or functions.
Event driven actions needs to be tested based on two factors
Events that trigger this action: With developer, QA has to test the event.
Action that performed by above event: testing the SP or functions.
Input item verification:
Process to verify the input items that are added into database. Also verify the fields with junk values, so the SQL injection should not be performed.
Process to verify the input items that are added into database. Also verify the fields with junk values, so the SQL injection should not be performed.
Test Stored procedure functionality
Check the functionality of SP.
Check the functionality of SP.
No comments:
Post a Comment