Results 1 to 4 of 4

Thread: Test scenarios for database testing

  1. #1
    Junior Member
    Join Date
    Apr 2006
    Answers
    1

    Test scenarios for database testing

    Can any one give me any two test scenarios for database testing of a web site and what are the possible testcases?

    Thanks and regards


  2. #2
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Test scenarios for database testing

    Quote Originally Posted by bvmanikyalarao View Post
    Can any one give me any two test scenarios for database testing of a web site and what are the possible testcases?

    Thanks and regards
    When we talk about database testing and database, It means we talk about database, and it's same for website and desktop application.
    Test cases can't describe here until and unless you will not post the scenario and requirement.


    How we can post the scenario without knowing your application use case documents and other related documents?

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  3. #3
    Junior Member
    Join Date
    Nov 2007
    Answers
    2

    Re: Test scenarios for database testing

    for eg when one does online shopping electronic invoice is provided with the ordernumber or the transaction number.
    to really understand whether the data has been inserted or updated in the database one has to query the database with sql statements to validate the data.
    if the response time for the page to get loaded takes too long than specified..then one of the reasons may be lack of indexing in the database....


    again test scenarios for data base testing shd be based on specification /requiremnts.


  4. #4
    Expert Member
    Join Date
    Oct 2007
    Answers
    375

    Re: Test scenarios for database testing

    Hi Rao,

    Database testing of a Web-based application would basically deal with Integrity checks as well updation checks of the Database.

    Like gettoknow pointed out - for instance we have an web-application dealing with Order booking, we might have different functionalities associated with the same like -
    1) Registered User ID
    2) Number of Items Ordered
    3) The pricing of each Item
    4) Total calcualtion etc.

    For each of these operations different tables in the DB would be getting updated. DB testing would basically involve -

    1) Taking a snapshot of the Database tables in terms of number of records
    present before carrying out the transaction
    2) Taking a snapshot after functionality is carried out using the UI. The
    number of records count should have gone up
    3) checking if Relational dependency of tables is properly getting executed.
    In sense when Orders table is updated, the inventorty table of the item
    should reflect a decrease in that specified item
    4) checking if intermediate updations occur in the DB prior to completion of
    the specified functionality. This should not happen

    These are the generic test scenarios. Other scenrios would be based more on test specification / functional specifications....

    Cheers...


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact