Static Verification Points
26
Chapter 2 - Basic Concepts
Static, Dynamic, and Manual Verification Points
In QualityArchitect, verification points can operate in three different modes--static,
dynamic, and manual--depending on how the verification point is invoked.
Static Verification Points
With a static verification point, the expected data object is captured the first time the
verification point is executed and is stored in the datastore as the verification point's
baseline. The expected data object does not change during subsequent executions of
the test script. When the verification point is executed again:
s
The baseline data object is retrieved from the datastore.
s
An actual data object is captured from the system-under-test.
s
The two objects are compared, and the result is logged.
Static verification points are regression-style tests in that the successful behavior of
the system is implicitly defined by the system's behavior the first time the verification
point executes. In other words, static verification points assume that the
system-under-test is functionally correct the first time you run the verification point.
QualityArchitect contains a user-acknowledgement flag that lets you interactively
accept or reject data as a baseline for a static verification point. With the flag enabled,
QualityArchitect will prompt you with the baseline data that you can accept or reject.
For details, see Verification Point classes in the online Rational Test Script Services for Java
and Rational Test Script Services for Visual Basic manuals.
To access the online documentation:
s
Click
Start > Programs
<
Rational ...
>
Rational Test > API > TSS for Java
or
s
Click
Start > Programs
<
Rational ...
>
Rational Test > API > TSS for Visual Basic.
where <
Rational ...
> is the name of the Rational product you have installed--
for example, Rational Suite DevelopmentStudio.
