How to do real database testing (10 tips to perform serious database tests) - Software Testing Space

Many (but not all) applications under test use one or more databases. The purposes of using a database include long-term storage of data in an accessible and organized form. Many people have only a vague idea about database testing. If you are serious about learning database testing, then read on...

Firstly, we need to understand what is database testing? As you would know, a database has two main parts - the data structures (the schema) that store the data AND the data itself. Let us discuss them one by one.

The data is stored in the database in tables. However, tables may not be the only objects in the database. A database may have other objects like views, stored procedures and functions. These other objects help the users access the data in required forms. The data itself is stored in the tables. Database testing involves finding out the answers to the following questions:

Questions related to database structure

1. Is the data organized well logically?

2. Does the database perform well?

3. Do the database objects like views, triggers, stored procedures, functions and jobs work correctly?

4. Does the database implement constraints to allow only correct data to be stored in it?

5. Is the data secure from unauthorized access?

Questions related to data

1. Is the data complete?

2. Is all data factually correct i.e. in sync with its source, for example the data entered by a user via the application UI?

3. Is there any unnecessary data present?

Now that we understand database testing, it is important to know about the 5 common challenges seen before or during database testing:

To read on and know the 10 tips follow the link:

Source: Software Testing Space


Popular posts from this blog

XPATH for IE / internet explorer

RPA - Blue Prism, OpenSpan, Automation Anywhere vs UIPath