Explain me how to write db checkpoint scripts

Showing Answers 1 - 1 of 1 Answers

ashobb

  • Jan 19th, 2006
 

About Standard Database Checkpoints

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.

There are two types of standard database checkpoints: Default and Custom.

You can use a default check to check the entire contents of a result set, or you

can use a custom check to check the partial contents, the number of rows, and

the number of columns of a result set. Information about which result set

properties to check is saved in a checklist. WinRunner captures the current

information about the database and saves this information as expected results. A

database checkpoint is automatically inserted into the test script. This checkpoint

appears in your test script as a db_check statement.

 

For example, when you check the database of an application for the first time in

a test script, the following statement is generated:

db_check("list1.cdl", "dbvf1");

where list1.cdl is the name of the checklist containing information about the

database and the properties to check, and dbvf1 is the name of the expected

results file. The checklist is stored in the test?s chklist folder. If you are working

with Microsoft Query or ODBC, it references a *.sql query file, which contains

information about the database and the SQL statement. If you are working with

Data Junction, it references a *.djs conversion file, which contains information

about the database and the conversion. When you define a query, WinRunner

creates a checklist and stores it in the test?s chklist folder. The expected results

file is stored in the test?s exp folder. For more information on the db_check

function, refer to the TSL Online Reference.

When you run the test, the database checkpoint compares the current state of the

database in the application being tested to the expected results. If the expected

results and the current results do not match, the database checkpoint fails. The

results of the checkpoint can be viewed in the Test Results window.

If need some more information mail me:

ashok.bheeman@wipro.com

 

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions