| || |
Testing Databases (Was \"Re: Postings\")
User MArk B. (email@example.com) posted:
Could you be just a little bit more specific? Like Max said, it depends on
what you want to do.
A question like this is kind of like asking for directions with the
statement, "I'm lost.". How do you answer that kind of a question? Point the
guy at a map store? Intentionally give him bad directions?
Try to clear it up just a bit. If you don't know exactly where you are
trying to go then try to provide a little clarification. "I'm looking for a
place to eat." is a fairly helpful to the person being asked for directions.
"I'm looking for a place to eat that serves Italian food that will let
someone in that's dressed like I am." is more helpful.
I'm not intentionally ragging on you Praveen. Please try to take this with
the intended good intentions.
"Praveen" <firstname.lastname@example.org> wrote in message
Re: Testing Databases (Was \"Re: Postings\")
User Tom Ba (email@example.com) posted:
Sounds like good stuff, Max.
Now, in other related matters,
given x hefty number of interfaces to test,
each with an interface document
which describes each column and its attributes (width, data type etc),
(and which easily could be put into a spreadsheet)
has anyone created some routines to read each interface spreadsheet
and test the incoming/outgoing data to
see if it is as it should be?
If so, kindly send it to Tomba or Paul
Downes for immortalization in the RationalUsers library.
----Original Message Follows----
Reply-To: "SQA Suite Team Test Users" <firstname.lastname@example.org>
To: "SQA Suite Team Test Users" <email@example.com>
Subject: RE: Postings
Date: Wed, 13 Jun 2001 15:08:53 -0400
I verify that data transformation from one database to another is performed
correctly and that tables have been updated as anticipated. I do so by
obtaining baseline from the source database and compare against actuals on
the destination database. The data is not in the same table structure so i
use different sql to retrieve the data on each of the databases.
How do you anticipate testing the database, white-box style using stored
procedures or objects or using the GUI? You need to define what it is you
are planning on testing.
If its by performing actions in the GUI, then you verify the database to
ensure that table updates have been properly performed. Example:
Perform action A Verify table X is updated as anticipated
Perform action B Verify table X and Y are updated as
I would say the anticipated results should as specific as required based on
whether you are testing on a database with a pre-defined base state or
whether it's on any database in any given state.
Depending on the scope of your testing, you may wish to verify that the size
of columns conform to some database structure document.
Column Style_code must be 5,0 numeric.
Style_description must be 25,0 numeric.
Retail_cost must be 12,2 decimal.
If you are testing for consistency in naming, you may wish to ensure that
column names conform to a standard. You might say a relational database
usually takes care of this, but for instance our database is not relational,
but the database rule validations are done in objects to improve on
performance since each database hit is a time consumer.
Ensure use of style_description (as opposed to style_desc)