Tutorial-8 How to use Verification Point Comparator Utility of RFT for comparing the Verification Point Data
A suggestion of great value:
Before practicing these Tutorials on “Rational Functional Tester – IBM RFT”, it is recommended that you acquire a preliminary working knowledge of using this wonderful tool –“Rational Functional Tester”. This can be easily attained by careful study of the“Frequently Asked Questions � FAQ�s” brought to you by this web site for the first time by Clicking on the following link:
Learn the Basics of RFT through FAQ’s
<<<<<<<< =========== >>>>>>>>
We use the “Verification Point Comparator” for comparing the verification point data after playing back a script with a verification point and to update the baseline file.
In case the verification point happens to fail, the “Comparator” displays both types of values
i.e. the expected and actual ones, so that we can draw a comparison. This provides us adequate information for updating the baseline file with the actual values from the actual file.
The Comparator can be opened by either of the following methods:
1) Double-clicking the verification point in the RFT log in the “TestManager”.
2) Clicking the View Results link in the RFT HTML log.
The Title of the Verification point gets displayed in the “Comparator” banner.
This short tutorial presents a simple method of using Verification Point Comparator Utility of RFT for comparing the verification point data
Following are the steps to compare and update the verification point data using the Comparator:
Step 1: Record a script in RFT and ensure that it must have at least one verification point.
Step 2: Play back the script containing the verification point on a new build of the application under test.
Step 3: View the log of the concerned playback after it gets finished.
Step 4: Open the “Comparator” from the log & view the verification point by the following.
a) In case of use of the TestManager log: Double click the verification point in the “Event Type” column. Expanding the Script Start command can enable us to see the verification point.
b) In case of use of the HTML log: Click the “View Results” link. At this stage we are likely to get a Java plug-in error. Thus to avoid this error, ensure that the Java plug-in is properly configured.
The Verification Point Comparator opens to display that verification point.
Step 5: We may encounter failure of verification points. The failed verification points can be handled by:
a) In case of failure of one verification point while using log in RFT Java Scripting:Select the log in the RFT Projects view. Then, right-click the log, and click “Failed Verification Points”.
b) In case of failure of one verification point while using log in RFT VB.NET Scripting:
Select the log in the Solution Explorer, right-click the log, and click “Failed Verification Points”..
c) In case of failure of multiple verification points while using log: The wizard of Results for Verification Points shall open. Click the desired failed verification point in the list and click“View Results” or “Finish”.
The Verification Point Comparator opens to display the concerned verification point. The Comparator displays the expected and actual data values. The difference between the expected and actual data values is that we performed the test with some expected values. However the actual values were captured in the application during the playback.
For failed verification points, the differences are indicated in red.
Step 6: Understanding of display structure for expected versus actual values:
a) For Properties, List, Table and data Text type verification points: The expected values are displayed on the left and the actual values are displayed on the right:
b) For Menu Hierarchy Properties and Tree Hierarchy type verification points: The expected and actual values are shown contiguously. The expected values of the differences are shown in Red, and the actual values of the differences are shown below them in Green.
Step 7: View the two data files to draw a comparison of differences between the expected and actual files. By close analysis of the differences in the Comparator, we can find out if they are intentional changes to the application or are real defects.
For navigating through the differences, we can use the navigation buttons on the toolbar above the data display.
Step 8: We may need to edit the baseline file to update the information for future playbacks. For this we need to load the baseline file. Click “File” > “Baseline” or click the button “Load Baseline to Edit” available on the toolbar.
The baseline file replaces the expected file on the left side of the display.
Step 9: Editing of items in the data:
a) For individual items in the data: We can edit them in the baseline (left) column of the display. Click “Save”, after completion.
b) For a Text type verification point: Click “Edit Text” to launch the text editor to make the changes.
c) For all other verification point types: We can edit directly in the baseline data display.
Step 10: Replacement of Baseline file:
a) For a properties verification point, updating of the baseline value is to be done in case difference is observed in the baseline value and the actual value for a particular property.
In the Verification Point Comparator, Right-click the property where the values are observed to be different, and click “Replace Baseline on Current Selection”.
b) In case all the differences reflect intentional changes to the application under test, and we want to update the baseline to reflect the changes, we need to use the “Replace Baseline with Actual Value” toolbar button to replace the entire baseline file.
c) In case we have made any individual changes to the baseline data file without the use of “Replace Baseline with Actual Value” command, click File > “Save” to save the changes.
Step 11: We can come out of the “Verification Point Comparator” after finishing the comparing and updating operation on the verification point data, click “File” > “Exit” to exit the Verification Point Comparator
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.