In ClassicsA, the name of the password field is Remember Password. In ClassicsB it is Remember The Password. When you played back the script on ClassicsB, the object recognition did not match exactly because of this difference.
The cursor moves to the left margin of that line number.
RememberPassword().clickToState(SELECTED);This line represents your click on the password check box. This line in the script shows which object is failing. Now you can look for that object in the object map.
Notice that all the objects change to black text. The text is blue (to indicate new objects) until you accept the objects in a map. You should accept the objects the first time you look at a newly created object map.
You can see that this is the object from ClassicsA, because it says Remember Password in the text property. This is the "old" object. However, when you played back the script on ClassicsB, the text for that object changed, so Functional Tester recognizes it as a "new" object. You want to use the new object properties in this case, so you must add it to the map.
The Member Logon window opens.
This is the same as the Object Finder tool in the Select an Object page of the Verification Point Wizard.
After you select the check box, you'll see that the text property is now Remember The Password. Stretch the borders of the object map, if necessary, to see the properties.
The new check box object is now shown in the object map.
Now both the old and the new objects are listed in the map. You want to unify the two objects and take the properties from each that you want for the new object.
The Unify Test Objects wizard opens.
In the lower left section, the original object's properties are shown. It should be labeled "Source: RememberPassword." That is what the text was on the check box in ClassicsA. In the lower right section, it should be labeled "Target: RememberThePassword." That is what the text is on the check box in ClassicsB.
Because you dragged the old object to the new object, the new object's recognition properties are filled in at the top of the wizard. In general, Functional Tester puts the new properties at the top if they are the preferred properties. However, some old administrative properties might be preferred. For example, Functional Tester retains regular expressions in the old property set. To use a property from the old object, double-click that property in the grid of the old object and it will be copied up into the unified object. In this case, we want to use all the properties of the new object, which are already filled in.
All scripts that are affected by this change in the object map are listed. Only one script, Classics, is affected.
The script now passes with no warnings! Notice that the playback no longer pauses on the password check box object because the recognition properties now match.
This object unification feature is an easy way to update scripts when recognition properties of an object intentionally change. One of the major advantages of this feature is that if your object map is being used by many scripts, you could update them all when you make the change in the wizard. Instead of manually editing multiple scripts, you can make a change once in the map and the change propagates automatically to all scripts that use it. This feature can save you time.