What do we verify with the database checkpoint default and what command it generates, explain syntax?

What do we verify with the database checkpoint default and what command it generates, explain syntax?

    >  By adding runtime database record checkpoints you can compare the information in your application during a test run with the corresponding record in your database. By adding standard database checkpoints to your test scripts, you can check the contents of databases in different versions of your application.

    > When you create database checkpoints, you define a query on your database, and your database checkpoint checks the values contained in the result set. The result set is set of values retrieved from the results of the query.

    > You can create runtime database record checkpoints in order to compare the values displayed in your application during the test run with the corresponding values in the database. If the comparison does not meet the success criteria you.

    > specify for the checkpoint, the checkpoint fails. You can define a successful runtime database record checkpoint as one where one or more matching records were found, exactly one matching record was found, or where no matching records are found.

    > You can create standard database checkpoints to compare the current values of the properties of the result set during the test run to the expected values captured during recording or otherwise set before the test run. If the expected results and the current results do not match, the database checkpoint fails. Standard database checkpoints are useful when the expected results can be established before the test run.

      Syntax: db_check(checklist_file, expected_restult);

    > You can add a runtime database record checkpoint to your test in order to compare information that appears in your application during a test run with the current value(s) in the corresponding record(s) in your database. You add runtime database record checkpoints by running the Runtime Record Checkpoint wizard. When you are finished, the wizard inserts the appropriate db_record_check statement into your script.

      Syntax: db_record_check(ChecklistFileName,SuccessConditions,RecordNumber );

      ChecklistFileName ---- A file created by WinRunner and saved in the test\'s checklist folder. The file contains information about the data to be captured during the test run and its corresponding field in the database. The file is created based on the information entered in the Runtime Record Verification wizard.

      SuccessConditions ----- Contains one of the following values:

      A. DVR_ONE_OR_MORE_MATCH : The checkpoint passes if one or more matching database records are found.

      B. DVR_ONE_MATCH : The checkpoint passes if exactly one matching database record is found.

      3. DVR_NO_MATCH : The checkpoint passes if no matching database records are found.

      RecordNumber : An out parameter returning the number of records in the database. 

Date:2031-01-09 00:00:00

Post Your Answers

User Email:

User Name:

Related TESTING Subjective Links

TESTING Subjective interview questions and answers for experienced and fresher