Database Testing

[COLOR="DarkRed"]Shall testers need to do a Database Testing on an application?
1.What is the purpose of such a testing??
2.What all testing need to be done on DB??[/COLOR]

Database testing is very important part of testing.

Database is always on target for hackers and others.
You should always well test the database for security also.

Other tests on database are for data,

There should no loss of data when we save it.
Data limit allowed to save through UI should same; limit allowed by database.
more depends on application.

Good to see you back [B]JanBrijesh[/B]:D I was missing your posts...

Well, the questions asked were very clear. Why do we need database testing and what kind of testing we usually do in database testing. I think Brijesh's explaination has not covered all that was needed. So, decided to post an external article on this.

[B]What to test in DB testing?[/B]

[QUOTE]In DB testing we need to check for
1. The field size validation
2. Check constraints.
3. Indexes are done or not (for performance related issues)
4. Stored procedures
5. The field size defined in the application is matching with that in the db.
[/QUOTE]

[B]Why DB testing ?[/B]

Here's the link for a very good article regarding this.

[URL="http://www.agiledata.org/essays/databaseTesting.html"]http://www.agiledata.org/essays/databaseTesting.html[/URL]

I hope this makes one understand the concepts in DB testing.

Cheers!
Kalayama

Hi Rose,
Testers should do the database testing in the case of using database,
90% of the application using database.

For example, for web application or any other application some data should be stored in database, the tester is the responsible person for veryfying whether the data stored or not, and also verify that the stored data will be a valied data.

so tester or developer should know the database knowledge.

regards,
ayypss

[B][B][COLOR="Purple"]Thanks Kalayama for that article..It was worth reading

But letme tell u frankly that Iam new to DB testing....So before Testing a DB
I should know
1.Why shall I test a DB??If we can look in to the UI and see if the data we enter through UI is getting reflecting in the UI and
When we delete something from UI...it again can be seen in the UI...So Shall we need to test it to see that the data flow is proper??
2.What all other purposes Database Testing serve for??
(Its clearly mentioned in the article...but superficial for a beginner to understand)

Will be helpful if anyone explain it clearly[/COLOR][/B][/B]

DB testing is to test the impact of actions in the application on its database.:cool:

the list for "What to test in DB testing?" give by kalayama is correct.:D

Hi

check this link too.

[url]http://www.oracle.com/technology/oramag/oracle/05-jul/o45testing.html[/url]

I found it more rational.

can any body explain in detail database tesing

Relational database management systems (RDBMSs) often persist mission-critical data which is updated by many applications and potentially thousands if not millions of end users. Furthermore, they implement important functionality in the form of database methods (stored procedures, stored functions, and/or triggers) and database objects (e.g. Java or C# instances).

The best way to ensure the continuing quality of these assets, at least from a technical point of view, you should have a full regression test performed on each build for the Database.

Noe lets see DBTesting in terms of Testing methods :

[B][U][COLOR="Red"]Black-Box Testing (--at the Interface) [/COLOR][/U][/B]
-O/R mappings (including the meta data)
-Incoming data values
-Outgoing data values (from queries, stored functions, views ...)

[COLOR="Red"][B][U]White/Clear-Box Testing (--Internally Within the Database) [/U][/B][/COLOR]

-Scaffolding code (e.g. triggers or updateable views) which support refactorings
-Typical unit tests for your stored procedures, functions, and triggers
-Existence tests for database schema elements (tables, procedures, ...)
-View definitions
-Referential integrity (RI) rules
-Default values for a column
-Data invariants for a single column
-Data invariants involving several columns


this was a little abt DB testing if you wanna more then can contact me with your Qs

can anyone give me a simple example for how to do database testing ,and also one testcase related to database testing

As per my knowledge the Data base testing is done when the test data is not provided from the developer to link the fileds and to do verification of the same.

For this we mainly need SQL. To get the information from the data base that is required for our application.

Regards,
Sudha

[QUOTE=rose;7519][B][B][COLOR="Purple"]Thanks Kalayama for that article..It was worth reading

But letme tell u frankly that Iam new to DB testing....So before Testing a DB
I should know
1.Why shall I test a DB??If we can look in to the UI and see if the data we enter through UI is getting reflecting in the UI and
When we delete something from UI...it again can be seen in the UI...So Shall we need to test it to see that the data flow is proper??
2.What all other purposes Database Testing serve for??
(Its clearly mentioned in the article...but superficial for a beginner to understand)

Will be helpful if anyone explain it clearly[/COLOR][/B][/B][/QUOTE]

What so ever you are talking about in what we can test externally see the behavior of database.
But what's happening in real , how you will know that.
I give you an example.

I was testing an application where during registration, an hash key is generated for verification purpose,This key generated is of size 16 characters always, but space allocated for it in database is of 50 characters, which is again a bug (loss of memory).That's why we need it to test internally.

What is scaffolding

Supporting test code, called scaffolding.It is sometimes necessary to support an individual test.