Professional Documents
Culture Documents
Database Checkpoint
Database checkpoint
Note:
We set the expected data in the Database Checkpoint Properties dialog box.
Note:
For the Mtours Flights example the mercurytours datasource is used
Note:
The parameterized checkpoint fails when the
value passed as a parameter appears
before the row which has been
parameterized in the actual table
Case Study
• Aim: To validate the user id entered initially.
– We should see to it that if the user id is valid and exists in the database. If it
exists the test goes to completion and the user can book a ticket else the
test fails.
– The case study needs to be implemented using the Wizard as well as using
VB script.
Hints:
– While implementing using the wizard Parameterize the checkpoint
– While using VB script use CreateObject method (ADO methods).
Additionally to display events use Reporter.ReportEvent method
Questions?
Q & A….
Session Wrap-up
• We use database checkpoints to check databases
accessed by your application and to detect defects.
• There are two ways to define a database query:
– Use Microsoft Query.
– Manually define an SQL statement.
• The checkpoint can be parameterized
• The match between the actual value and expected value
can be based on row column match (position taken into
consideration) or based only on values irrespective of
position.
• The checkpoint can easily be created using the wizard, but
another option would be to do the same using VB script