Prepare for your Next Interview
|
Welcome to the Geeks Talk forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
This is a discussion on Test scenarios for database testing within the Test Cases forums, part of the Software Testing category; 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...
|
|||||||
|
|||
|
Re: Test scenarios for database testing
Quote:
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?
__________________
-- Brijesh Jain |
|
|||
|
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. |
|
|||
|
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...
__________________
Regards, V.Umesh Krishnan QA Consultant |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| test scenarios | sakshi_2801 | Testing Issues | 8 | 01-01-2009 06:51 AM |
| If test case required for testing always post test scenario. | jainbrijesh | Test Cases | 15 | 12-30-2008 10:55 AM |
| Database Testing | rose | Testing Issues | 13 | 11-22-2007 06:14 AM |
| Test Scenarios | Navita | Testing Templates | 7 | 08-17-2007 10:26 AM |
| database testing | prasad79 | Testing Issues | 2 | 03-26-2007 06:06 AM |