Quality Testing

Quality is delighting customers

Can any one know how to test database manually

Views: 1647

Reply to This

Replies to This Discussion

There are two things whether you want to test database itself or you want to check any application which is using database.

Second one is simple and can find lot of docs on net.

First one where you want to test the database itself it depends upon which functionality you want to test.

For example, In my past experience I was doing the testing of PSQL ( database) for client Pervasive. There is two ways one is white box testing where normally we create the automation script in C++, Perl, shell script  to check the database internal architecture (white box testing). We should know the exactly how the code is flowing to create the database features.

another one is black-box testing where use the database itself to check the features, like table design, table property, data types.

Now my question is here which database you want to test?

@ Shailesh Jain -  if u hav any material or doc regarding Database testing plz fwd it to my email id - ' rsrajez@gmail.com '

thanks in advance


kindly to me also skush05@gmail.com

Hi, Shailesh

I am talking about how to test database manually of websites and web applications. And please if you have some material on it than send it to my id jasminesharma224@gmail.com.

Thanks in advance


if it is to see the recoreds stored in database and what shown in UI is correct or not?? then if u r using FIles rather than sqlserver etc.. decrypt those files and see w.r.t UI data.

hi jasmine..


in database testing we have to do follwoing checks:

1) Verfication and validation of Data i.e insert data from front end and check at database with the help of toad/sql developer / oracle prompt.

2) Trigger testing i.e to check action

3) Business logic updation in database

4) View Testing

5) Database LInk / DBlink Testing

6) Cursor testing

7) Migration testing


Database testing is very wast..i have just mention very few points.

if u have any query pls. feel free to ask samarchauhan@yahoo.com





Features to be checked

Steps to be Followed

Check for Foreign key:

Foreign keys should not contain NULL values

Check for Primary key:

Data type of Primary key and the same key acting as foreign key should be same in two tables.

Check for mandatory fields on UI:

 'Allow Null' condition should be checked at data base level for mandatory fields on UI

Check for all fields:

Field length should be sufficient in size especially when field is going to get grown at run time(depending on master entries).

Check for all fields:

LTRIM and RTRIM should be performed on data before inserting data into data base

Check for each field and UI element:

Field length of field in data base and on UI(if mentioned) should be same.

Check for Foreign key:

Foreign key should be marked as FK in table design so that field will not allow NULL to be entered.

Check for all fields:

Null' as value should not be allowed in data base, validations should be made so as to avoid user to enter such data.

Check for Primary key:

For Primary key 'Allow Null' condition should not be allowed.

Check for Primary key:

Data type of Primary key should be selected as per the project requirement (unique identifier or int as per the requirement)

Check for all fields:

Allow Null condition should be checked in Stored Procedures as well as data base level.

Check for all fields:

Data types of each field should be selected taking into consideration the values it is going to store.(like some times tinyint or smallint suffice instead of defining field as int)

Check for all fields:

While allowing NULL values on particular field verify that that field is not mandatory.

Check for each field and UI element:

Field length specified on UI should be same with the field length specified in table design to store same element from UI into database.

Check for All tables which are associated with some other table:

Suitable option should be chosen from separate mapping table and foreign key according to the requirement.

 Enable logging of all user login events

Verify that log events are added in database for all login events.


You have added very good point. I think I have some doc. Give me one day I will share the doc with all.


My email id is joshi.jugal@gmail.com , please also send me some document related to the database testing.

Thanks in advance

jugal joshi

please send me also at Miteshahir4@gmail.com.........

  Hi ,,, 

Good web applications are generally implemented using "Three-Tier Architecture". In this we have three different layers which perform independent functions.

1. Presentation Layer :- It consists of UI of the web application which is developed using HTML, CSS which are markup languages.

2. Business Logic Layer:- It implements your actual logic of the web service that you want to offer to users. Business Logic is written using normal programming language like Java, Python etc. It will perform all the job of updating databases or sending data to UI from Database. Business Logic is implemented on Application Server.

3. Database Layer :- Last layer is actual databases and it stores all the data of the user application.

Consider the gmail web application ,,when you compose a message and send ,the message will be stored in sent folder ,,,that's how we can conform that database is working fine...

Data consistency is very important in web application. Check for data integrity and errors while you edit, delete, modify the forms or do any DB related functionality.
Check if all the database queries are executing correctly, data is retrieved correctly and also updated correctly. More on database testing could be load on DB, we will address this in web load or performance .


TTWT Magazine





© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service