background image
<< Static Verification Points | The Query Builder >>
<< Static Verification Points | The Query Builder >>

Dynamic Verification Points

Test Script Services
Dynamic Verification Points
With a dynamic verification point, the expected data object is passed to the
verification point at execution time. This expected data object is not managed by the
verification point infrastructure and may be hard coded into the script, driven by
values in a datapool, or built using any other method chosen by the test script author.
When a dynamic verification point is executed, an expected data object is passed to
the verification point by the test script. The verification point captures an actual data
object from the system-under-test, compares the expected and actual data objects, and
logs the result. Dynamic verification points differ from static verification points in
that the successful behavior of the system under test is explicitly defined by the test
script author, not implicitly defined by a previous behavior of the system-under-test.
Manual Verification Points
With manual verification points, you as the scripter are responsible for providing
both the expected and the actual data objects. The verification point framework
simply compares the data objects that you provide and logs the results.
Database Verification Point
In this release, Rational has implemented a single verification point: the database
verification point. This verification point is used to validate the changes made to a
data source by the component-under-test.
With a static database verification point, the first time that you run a test, the data is
captured and stored in the datastore, thus establishing a baseline. Subsequent runs
will show a pass in the Rational Test Log window if the returned values are the same
as the values in the baseline. With a dynamic database verification point, the test
script itself constructs the expected value.