What we normally check for in the Database Testing?
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.
Based on the testcases written for the module, we have to cover the UI testing, Whichever modules we are testing, our main focus should be on database.
1) What are tables affected?
2) From where the data is being retrieved and displayed on the UI and is it correct?
3) Above all we should know how to connect to the database? ability to write simple queries to retrieve data and manipulate the data using DML operations. Functional flow should be very well known!
4) Good knowledge on table level, column level constraints, ability to understand and execute complex queries related to joins is added advantage.
Above answer was rated as good by the following members: sindoo, goksn
RE: What we normally check for in the Database Testing?
Database testing involves some indepth knowledge of the given application and requires more defined plan of approach to test the data. Key issues include : 1) data Integrity 2) data validity 3) data manipulation and updates.
Tester must be aware of the database design concepts and implementation rules
RE: What we normally check for in the Database Test...
can you mention steps taken by a tester to test stored procedures..starting from connecting to database and so on..To make it easier to understand how to start tesing SP and Triggers.
RE: What we normally check for in the Database Test...
Stored procedure is nothing but a collection of different queries
this stored procedure is used to make the execution more easy instead of calling the query every time you can call the stored procedure directly by using its name.
1 
0