Santhosh

• Jul 12th, 2005

 

In DB Testing, basically all the events like Add, Delete, Update, Modify etc...

Phani Kumar

• Jul 26th, 2005

 

How to test Stored Procedures? send me Immediately

shankar

• Jul 31st, 2005

 

what r the documents supported for integration testing?

Kishore

• Aug 22nd, 2005

 

 
How to test Stored Procedures?

Anand Kulkarni

• Aug 22nd, 2005

 

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

Preston

• Oct 17th, 2005

 

how can i test the stored procs. anyone? thanx

anil

• Jul 4th, 2006

 

 Hi all,

  1) Display and change stored procedure variables.

  2) Stop execution at any point.

  3) Alter Program logic.

Correct me if i am wrong.

Regards,

-Anil.

LoniT

 Profile Answers by LoniT Questions by LoniT

• Aug 1st, 2006

 

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.

Thanks.

Aruna Kumar G

• Aug 17th, 2006

 

Normally we check whether data would be saved properly in data base and retriving data from the data base.

That will be normally check for in the Data Base

dinesh.birla

• Apr 10th, 2007

 

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.

Babu Reddy

• May 2nd, 2007

 

1.To validate the Front end  data which is displaying is same as the Back end Data.
2.To Validate the extraction processes (nightly or scheduled), whether the correct data is comming in to our project Tables.

Jyothi_E

 Profile Answers by Jyothi_E Questions by Jyothi_E

• Jun 6th, 2007

 

Can you please explain me how to check for the "Indexes are done or not (for performance related issues)" and check constraints with an example to be much more clear about the concept. 

amitRanjan

 Profile Answers by amitRanjan 

• Aug 14th, 2007

 

As I know In database Testing

We generally check CURD Function

C-Create
U-Update
R-Retrive
D-Delete

This is the core functionality of Database .That we need to check

Thanks
Amit

KauShreya

 Profile Answers by KauShreya Questions by KauShreya

• Nov 3rd, 2008

 

We test Stored Procedure code is to call the procedure for the different combinations of input parameters so that it will behave as expected.
The second is to use the command window as a client, and call the procedures from there. This re-routes the server's error messages to the command line, where you can trap them to a file and read them outside Query Analyzer.

prasadmeduri

 Profile Answers by prasadmeduri 

• Feb 4th, 2009

 

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.

goksn

 Profile Answers by goksn 

• Sep 6th, 2009

 

In my experience , I have done the followign test activities as part of databaes application

*Data Integrity: Whether relationship between tables (as defined while designing tables) are getting respected after different equievalence classes of data.

*Data Validity: Whether data type/size validations are happening. Check,UNIQUE,PRIMARY KEY constraints are satisfied with different equievalence classes of data.

*Execution of stored procedures / Triggers: Testing whether data which arrived in database are getting processed under pre-defined/user-defined SQL stored procedures and triggers and proper Insert/update/delete operations are getting done.

*Checking daily job status: Whether daily jobs are getting done at pre-specified time (for e.g everyday morning 3:00 a.m USP_PROCESSDATA stored procedure is getting executed.

*Performance testing: Checking the impact of cluster and recommendation on 'which queries / stored procedures are taking more time to get executed'.

*Connectivity testing: Checking the connectivity between database and presentation layer.