Part1 -Database Testing

Welcome!
I am starting a series of threads in database testing for software test engineers. I have seen testers are struggling for database testing and they are very keen on learning of database testing. It is not true that they don’t know the database or the SQL, but they don’t know what exactly they need to test and why they need to test (some confusion is like data is there in database and so it is coming in Application and we should not test database)
I am starting a series of database testing concepts all based on practical and only practical knowledge, and no theoretical Gyan.

Part1

Here is a million dollar question :
Why we should do database testing ?
Here below is some of the answer ( might be many more)
1. To tell that -  data appears in application is correct or not

2. To tell that - data appears in UI is coming from database or developer has hardcoded the data in code( if data is hardcoded - it’s a very high severity and priority bug)

3. How to test ADD/EDIT /DELETE functionality ( ADD/EDIT /DELETE actually update database records - In case of ADD -new record in inserted with correct values , in edit it should edit the values and no record is inserted , in case of delete , it should delete the data or mark the data disable( soft delete or hard delete))

4. To Test reports data - where lots of data appears in consolidated format( In this case there is a great need of database testing like in DataWare Housing testing or in business intelligence Testing etc., if you dont know what is a difference in DWH and DB,don't worry,i'll explain in mu blog)

5. How to manipulate the data in database and get the desire result in Application UI( Like update the disable user so that they can login again )

6. How to replicate the scenario( by reverse engineering – Query in database and knowing the probable reason for failure in production environment where we can get the production log and database entry)

Above is some of the reason for database testing and there is many more.

Next series is a contiuation of database testing - how to perform database testing