| || |
User Aidy Rutter (AidyR@TrustMarque.com) posted:
I'm not receiving any postings, and I wondered who I get in touch with about
this? I can send but I don't receive. I've been in touch with the bloke in
IS, but he says it's nothing to do with our side.
Could you send any info to my personal address, else I wont get it.
User Simon P Garnett (email@example.com) posted:
I got your posting!
User Praveen (firstname.lastname@example.org) posted:
I need help in the intricacies of database testing. What actually goes in
the database testing, what attributes we should look for in testing the
database. Any links on these would be highly appreciated.
Thanks in Advance.
----- Original Message -----
From: "Simon P Garnett" <email@example.com>
To: "SQA Suite Team Test Users" <firstname.lastname@example.org>
Sent: 13/06/2001 2:40 PM
Subject: RE: Postings
User MArk B. (email@example.com) posted:
See if you can connect to the news group using outlook express.
"Aidy Rutter" <AidyR@TrustMarque.com> wrote in message
User Simon P Garnett (MMcNaughton@STSSystems.com) posted:
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)