DataBase Testing Roles and Responsibilities

"what kind of scenarios? about database connectivity? how do u import database dump, how do u export database dump? how do u create user schema? whats more....database testing is nothing abt integrity testing...to my knowledge third normal form best suits for database testing"


http://dbunit.sourceforge.net/intro.html

http://www.testinginstitute.com/display.php?id=DATF_MS

http://www.ldas-sw.ligo.caltech.edu/doc/testing/metadata.html

"In my opinion Database testing is one area where pure black box testing is completely inappropriate. You DO need database knowledge in order to test a database. Also some part of the testing could be carried out without any query: checking the data definitions, tables and columns data types, constraints,.

DB check is highly used to validate the Query & report screens ( depends on application ). collect the query from ur developer and execute it in toad by validating explain plan . here u have to notice the cost & full table scan access then provide your suggestion to fine tune that query.( Needs some knowledge abt SQL ).

another thing is u have to validate the column& data-type size. this should be sync with front -end.( depends on screen )

In multi user test, u have to validate whether they are locking the selected row in Table level or row level.

In DB testing we also 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.

Note: Stored procedure can be executed without back-end, i suggest you get db connection details, credentials, table names, procedure name and access to a query analyzer as toad, ms query analyzer then you do not need front end to test all data in a application......

there cannot be a sample query until you have all these details. If you are not good at database , ask your DBA to help you out. "