Database Testing

https://www.youtube.com/watch?v=epvNp7xLtg8

1)What is  a Database?

Database is an organized collection of data, which provides efficient retrieval of the data.

2) What is DBMS?

DBMS: Data base  Management System.  It is system of systematic  way of  Creating, Storing, Retrieving and Managing of data.

Ex: File system, XML

3) What is RDBMS?

Relational Database Management System: Is a database system based on relational model.

Ex: SQL Server, Oracle

4) What is Database testing?

Database testing is a process of testing the behavior of the database with reference to front-end web/desktop application. Any changes made in the front end should change backend and vice versa

• Data Integrity


• Data Validity


• Data base performance


• Testing of functions, procedure and triggers

 5) What do we need to check in Database testing ?

• Constraint check


• Verification of a field size and type


• Stored procedures, Triggers


• Performance based issues

6) How do you test Data Integrity? What do you take into consideration while verifying data Integrity? Give Examples.

• Verify any of the create, retrieve, update and delete operations (CRUD), should display and most recent values/Status of shared data on all the forms and screens. Data Consistency throughout the application.


• Verify blank value can be retrieved from the database.


• Verify each value is successfully saved to the database and truncation of strings and rounding of numerals occurs as per business requirements.


• Verification of data compatibility against old version of hardware or operating systems.


• Verifying the data Updated/modified and deleted from the front end are reflected in the backend.

7) How do you test Data validity ?

Field Level Validation

Form Level Validation
Data Saving Validation
Search Criteria Validation

8) How can you reduce data corruption which occurs by human errors?

Range Validation
Lookup Validation
Masked Input Validation

9) How will you plan Database performance Testing

• Set and define performance goals regarding load and response time.


• Define resources and build virtual machines to identify database behavior with different machine configurations.


• Create multiple virtual users to verify the response time for executing the transactions.


• Time taken by database to fetch specific records or number of records should be verified.


• Include editable transactions and non-editable transactions.


• Design test cases to identify the system breakpoint.

10) What will you consider while testing of procedure?

Relate to the business requirements.

Outputs:

Number of rows affected

Extracted records

Is supposed to do and not supposed to do.

Queries to test if stored procedure is extracting right data.
Parameters:
Check parameters if they are required.
Call stored procedures with valid ,invalid data and boundary data.

Return values:
When failure/success  occurs validate return value.

Error messages:
Make stored procedure fail and check for error messages.

Find out exceptions where stored procedure can fail.

11)Name and explain database testing validations?

Data Mapping: In the software application, data often travels back and forth from the backend Data Base to the user interface and vice versa.

a)To validate whether the fields in the User interface are mapped consistently with the corresponding Database table and also the fields within the table.

• Whenever  a certain action is performed in the front end of an application, a corresponding CRUD (Create, Retrieve, Update and delete) action gets invoked at the back end.


• ACID properties validation: Atomicity, Consistency, Isolation and Durability.


• Atomicity means that a transaction either fails or passes. If a transaction has multiple steps and any part of transaction fails means that the entire transaction has failed.


• Consistency: A transaction either creates new valid state of data or rolls back to the original state if any failure occurs.


• Isolation: A transaction in process and not committed should remain isolated from other transactions.


• Durability: Once a transaction is completed and committed, no external factors like power loss, technical failures like hardware crash, reboot, networking issues should be able to change it.


• Business rule Adherence

12) What SQL statements have you used for DB testing?

• DML: Update, Insert, Delete, select, Merge, Call


• DDL: Create, Alter, Drop, Truncate, comment, Rename


• DCL: Grant and Revoke


• TCL: RollBack, Commit

13) How do you test DB manually?

CRUD in the front end application and verify data is changed accordingly in the backend.

14) How Do you test Trigger?

By querying the common audit log where we can see triggers fired.

15) What is Data Driven testing?

Data driven testing is an automation testing, which tests the output and/or input values. These values are read directly from the data files rather than using hard coded values. The data files can be csv files, excel files, text files, data pools etc.