If we talk about the application as per today scenario, application getting more and more complex. Users main focus only to see the GUI because only with GUI, end user can interact with the application. GUI only display the result after doing some functionality in back end which will be happen due to Database so Database Testing is must in today scenario. Database Security, Validation is much needed part in today application because anyone can access your important data if your Database is not secure.
So in this article we will discuss about Database Testing.
Database Testing is the layered process. Database system consist of 4 layers in which first is UI layer then Business Logic Layer third is Data accessing layer then 4th is Database itself.
In Database Testing we will check the Data Mapping, ACID (Atomicity, Consistency, Isolation and Durability), Data Integrity, How much database handling the Load and Responsiveness.
Now first Understand the above keywords
Data Mapping
In Data mapping (Schema Testing) we should ensure that schema mapping between Front End and Back end should be similar because in software data move from back end to front end and front end to back end several times so both schema should be same.
We can review this will following steps;
Atomicity
Transaction contains some Statements. Atomicity simply gives that either your Transaction "PASS" or "FAIL" , there is not a middle situation. If anyone statement during transaction is Failed then complete Transaction get Failed and Database left unchanged. An Atomic system must guarantees in every system like Power Failure, Plane Crashes etc. Usually we call it All-Or-Nothing rule.
An example of an atomic transaction is a monetary transfer from bank account A to account B. It consists of two operations, withdrawing the money from account A and saving it to account B. Performing these operations in an atomic transaction ensures that the database remains in a consistent state, that is, money is neither lost nor created if either of those two operations fail.
Consistency
Any Type of Transaction occur in User Interface then Consistency ensure that Database always be in Valid and Legal states. This prevents database corruption by an illegal transactions, but does not guarantee that a transaction is correct.
For example, if a column is constrained to be NOT NULL and an application attempts to add a row with a NULL value in that column, the entire transaction must fail, and no part of the row may be added to the database. In this example consistency was not handled.
consistency means that any defined checks and constraints are satisfied after any transaction
Isolation
If we talk about Transaction so sometimes multiple transaction occur on same time or sometimes transaction occur one after another. so isolation ensure that concurrent execution of transaction leaves Database in same state that would've been obtained if the transactions were executed sequentially.
Example If suppose 2 friends who have a Joint account in a Bank and they both performing Transaction from different ATMs on same time then Isolation ensure that these two transactions operate on he database in an isolated manner. Database perform first transaction and then second then third in a sequential way. If Transaction is not isolated then both execution perform on same time or it may possible that account have less money but total both requesting more and they get it.
Durability
Durability guarantees that once a transaction has been committed, it will remain committed even in the case of a system failure or Power Failure or any other reason. So durability ensure that Data should not get lose in any case if Transaction occur.
If you are buying something from an online shop, if he system show that your credit card is processed and the order is placed, then that order remain in place, even if he system crashes.
Data Integrity
Data Integrity ensure that due to any Transaction if any data is updated then that updated data should be reflect in all screens. It means if any transaction occur in one table in Database then in corresponding table also that transaction should reflect and that updated value should get update.
any Value can be update in Database due to CRUD operation.
Business rule conformity
Tester need to check the Business Logic and Business logic will be varies as per the Software so Tester need to write the complex queries to check the Trigger, Stored Procedures, Relational Constraints to check the Database.
So in this article we will discuss about Database Testing.
Database Testing is the layered process. Database system consist of 4 layers in which first is UI layer then Business Logic Layer third is Data accessing layer then 4th is Database itself.
In Database Testing we will check the Data Mapping, ACID (Atomicity, Consistency, Isolation and Durability), Data Integrity, How much database handling the Load and Responsiveness.
Now first Understand the above keywords
Data Mapping
In Data mapping (Schema Testing) we should ensure that schema mapping between Front End and Back end should be similar because in software data move from back end to front end and front end to back end several times so both schema should be same.
We can review this will following steps;
- First you can check that all input field which are taken in front end should also taken in back end. Let's understand it with an example suppose in front end there are 4 fields in which user need to fill Name, Email address, Date of Birth and Password . Now these all 4 fields should be in Back end also. Generally this information given in software documents.
- Whenever any CRUD operation( Create, Retrieve, Update and Delete) perform in UI then in Database also same operation invoked in database.
- Table Schema of both front end and back end should be compatible. If Database administrator delete any table or perform any change in table structure then Tester should ensure that due to particular change related table, Stored procedures and Views should work as was working.
Atomicity
Transaction contains some Statements. Atomicity simply gives that either your Transaction "PASS" or "FAIL" , there is not a middle situation. If anyone statement during transaction is Failed then complete Transaction get Failed and Database left unchanged. An Atomic system must guarantees in every system like Power Failure, Plane Crashes etc. Usually we call it All-Or-Nothing rule.
An example of an atomic transaction is a monetary transfer from bank account A to account B. It consists of two operations, withdrawing the money from account A and saving it to account B. Performing these operations in an atomic transaction ensures that the database remains in a consistent state, that is, money is neither lost nor created if either of those two operations fail.
Consistency
Any Type of Transaction occur in User Interface then Consistency ensure that Database always be in Valid and Legal states. This prevents database corruption by an illegal transactions, but does not guarantee that a transaction is correct.
For example, if a column is constrained to be NOT NULL and an application attempts to add a row with a NULL value in that column, the entire transaction must fail, and no part of the row may be added to the database. In this example consistency was not handled.
consistency means that any defined checks and constraints are satisfied after any transaction
- Particular column should be stored value only defined type( INT defined column should stored only INT type value)
- Primary Key and Unique key should be unique
- check constraints are satisfied
- Foreign Key constraints are satisfied
If we talk about Transaction so sometimes multiple transaction occur on same time or sometimes transaction occur one after another. so isolation ensure that concurrent execution of transaction leaves Database in same state that would've been obtained if the transactions were executed sequentially.
Example If suppose 2 friends who have a Joint account in a Bank and they both performing Transaction from different ATMs on same time then Isolation ensure that these two transactions operate on he database in an isolated manner. Database perform first transaction and then second then third in a sequential way. If Transaction is not isolated then both execution perform on same time or it may possible that account have less money but total both requesting more and they get it.
Durability
Durability guarantees that once a transaction has been committed, it will remain committed even in the case of a system failure or Power Failure or any other reason. So durability ensure that Data should not get lose in any case if Transaction occur.
If you are buying something from an online shop, if he system show that your credit card is processed and the order is placed, then that order remain in place, even if he system crashes.
Data Integrity
Data Integrity ensure that due to any Transaction if any data is updated then that updated data should be reflect in all screens. It means if any transaction occur in one table in Database then in corresponding table also that transaction should reflect and that updated value should get update.
any Value can be update in Database due to CRUD operation.
Business rule conformity
Tester need to check the Business Logic and Business logic will be varies as per the Software so Tester need to write the complex queries to check the Trigger, Stored Procedures, Relational Constraints to check the Database.
Comments
Post a Comment