Join the social network of Tech Nerds, increase skill rank, get work, manage projects...
 
  • Test Data Preparation Guidelines

    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 174
    Comment on it

    In the First Stage

    1.One dedicated resource should be allotted for preparing the test data.
    2.The dedicated resource should understand the system as a whole.
    3.Identification of total no. of Database tables.
    4.Listing of Master tables.
    5.Learning about each and every data field attributes.
    6.Idetify User/System maintainable tables.
    7.Static data should be prepared for all the master tables.
    8.Data should be valid and more meaningful.
    9.Real data can be requested from developers/client, atleast sample data.
    10.Once the application environment is up ,insert the data from the front end interface and make sure that is update in the tables.

    With respect to business functionality systems:

    11.Before entering into real time testing ,try to conduct the dry run.
    12.Collect the Business Life Cycle from the client/developer/test engineer.
    13.After thorough study of BLC try to collect the no. of screens that falls in each BLC.
    14.Prepare the test data for each screen.
    15.When populating the test data , take care of parent child tables and referential integrity that have been defined in Data structure.
    16.If we found a bug , before showing it to the client just cross check with Test data .Some times because if irregular test data the test case may fail.
    Steps for the format Creation of Test Data
    17.Idetify the different type of users and their priveileges.
    18.Identify the associated tests w.r.t particular user.,br> 19.Identify the different field types.
    20.Inserting the actual data.
    21.Finalize the total columns that is required.
    22.Insert the data for 2 BLC's and do the changes as per the requirement.

    Steps to be taken care for populating the Test Data:

    23.Understand the users from the projected system point of view.
    24.Customer 1, one who will do regular payments.
    25.Customer 2, one who will do irregular payments.
    26.Customer N, one who will do regularly irregular payments.
    27.Consider logical days and logical operations.
    28.Identify data for different Sector/Segment/Sub Segment.

    Steps to prepare Test Driver
    29.Try to identify from which system input is coming.
    30.Create table with n-fields which will fit the output of respective system.
    31.Once after input is received insert data in the system and cross check with the output, which is processed ,on the basis of credit program.

    Steps to create Test Stub

    32.Create the simple interface , which will comprise required fields to test the database.
    33.Input the data and cross check whether that is updated in the database.

 0 Comment(s)

Sign In
                           OR                           
                           OR                           
Register

Sign up using

                           OR                           
Forgot Password
Fill out the form below and instructions to reset your password will be emailed to you:
Reset Password
Fill out the form below and reset your password: