- Database Testing Tutorial
- Database Testing - Home
- Database Testing – Overview
- Database Testing – Types
- Database Testing – Processes
- Database Testing – Techniques
- Database Testing – Scenarios
- Database Testing – Objects
- Database Testing – Data Integrity
- Database Testing – Data Mapping
- Database Testing – Performance
- Database Testing – Tools
- Database Testing – Backup
- Database Testing – Recovery
- Database Testing – Security
- Database Testing – Challenges
- DB Testing - Interview Questions
- Database Testing Useful Resources
- Database Testing - Quick Guide
- Database Testing - Useful Resources
- Database Testing - Discussion
Database Testing – Scenarios
In this chapter, we will see some common database test scenarios with respect to various testing methods.
Structured Database Testing
Common database scenarios with respect to Structured Database Testing are given below −
Verifying the name of database, verifying the data device, log device and dump device, verifying if enough space allocated for each database and verifying database option setting.
Names of all the tables in database, column names for each table, column types for each table, null value check or not. Verify the Key and indexes in each table: Primary key for each table, foreign keys for each table.
Data types between a foreign key column and a column in other table Indices, clustered or non-clustered unique or not unique.
Functional Database Testing
Common Database Test scenarios with respect to Functional Database Testing are −
Finding out the schema, triggers and stored procedures responsible to implement that function and make them into a functional group and then each group can be tested together.
Check data flow and see where you can check the data. Start from the front-end.
Non-Functional Database Testing
Common Database Test scenarios with respect to Non-Functional Database Testing are −
Write test scripts to try major functions and every function must be checked at least once in a full cycle.
Perform the test scripts again and again for a specific time period.
Verifying the log files to check any deadlock, failure out of memory, data corruption, etc.
Write queries from a front end and issue the searches. Pick up an existing record, change values in some fields and save the record. (It involves UPDATE statement or update stored procedures, update triggers.)
Insert a new menu item in a front-end window. Fill in information and save the record. (It involves INSERT statements or insertion stored procedures, deletion triggers.)
Pick up an existing record, click on the DELETE or REMOVE button, and confirm the deletion. (It involves DELETE statement or deletion stored procedures, deletion triggers.)
Repeat these test-cases with invalid data and see how the database responds.