Use a Data verification point (State) to test the state of a check box or a toggle button in your application. When you record the verification point, a baseline of the state data is created. Every time you play back the script, the data is compared to see if any changes have occurred, either intentionally or unintentionally. This is useful for identifying potential defects.
To create a Data verification point (State):
In Functional Tester, Java Scripting, click the Record a Functional Tester Script button on the Functional Tester toolbar or the File > New > Functional Tester Script Using Recorder menu command to start recording a script. In Functional Tester, VB.NET Scripting, click the Record a Functional Tester Script button on the Functional Tester toolbar or the File > New > Add Script Using Recorder menu command to start recording a script. For more information, see Recording a Script.
From the Recording toolbar, click Start Application to start your test application. For more information, see Starting Your Test Applications.
Locate the check box or toggle button in your application to test.
From the Recording toolbar, click Insert Verification Point or Action Command.
On the Select an Object page of the Verification Point and Action Wizard, use the Object Finder to select the field or area in your application that contains the check box or toggle button to test. For more information, see the Select an Object.
After you select the check box or toggle button, one of the values in the Object recognition properties grid should be the word "checkbox" if it is a check box, or "togglebutton" if it is a toggle button. Verify this and click Next.
On the Select an Action page, the Perform Data Verification Point option should be selected, the first option on the page.
CheckBox Button State is the Data Value listed for a check box. If you are testing text on a toggle button, select the Toggle Button State test. The list of tests in the Data Value field depends on information provided by the object proxy. Values other than those described here may be shown.
In the Verification Point Name field, accept the default suggestion, or type a new name. This name must comply with standard Java naming conventions. The default name is based on the name of the object and the data value you chose to test.
Use the Include Retry Parameters to set a retry time for a verification point during playback to check for its existence. The retry option is useful when playback does not find the verification point in your application. To set a retry time, either use the default or set your own time. Maximum Retry Time is the maximum number of seconds Functional Tester retries for the verification point to appear in your application during playback. Retry Interval is the number of seconds between times that Functional Tester checks for the verification point during the wait period.
When you select Include Retry Parameters, Functional Tester checks for the existence of the verification point in your application every 2 seconds, for up to 20 seconds. To set your own time, clear the default fields and provide your own values for Maximum Retry Time and Retry Interval. When you click Finish, the retry for verification point is written into your script, and occurs on future playbacks.
After you accept or edit the fields, click Next.
(Optional) Edit the data. On the Verification Point Data page, the button states display in a list format. You can select which button states get tested in the list in this area.
After you view or select the button states, click Finish.
The verification point is recorded and added to the script.
After you record any other verification points or actions, end your recording by clicking the Stop Recording button on the Recording toolbar.
After you finish recording, you can open the Verification Point Editor any time to edit this data.
You can also create a verification point by scripting it manually. For Functional Tester, Java Scripting information on adding manual and dynamic verification points, see Adding Manual and Dynamic Verification Points. For Functional Tester, VB.NET Scripting, see Adding Manual and Dynamic Verification Points.
Also see the vpManual() and vpDynamic() methods of RationalTestScript documentation. RationalTestScript is in the API documentation. For Functional Tester, Java Scripting, click Help > Functional Tester API Reference. For Functional Tester, VB.NET Scripting, click Help > Contents > IBM Rational Functional Tester Help > API Guide. Your script can access the same information as the verification points. See the TestObject getProperty() and getTestData() methods.
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.