Relevant for: GUI tests and components
|Using programmatic descriptions||
When running in Maintenance Mode, if a step contains a programmatic description for an object that is not found in an application, it may take a while for Maintenance Mode to indicate there is a problem. If you use the option to point to the object, it may take a while for Maintenance Mode to reopen afterward.
|Objects without mandatory or assistive properties||
When the Maintenance Run Wizard cannot find an object, and the test object description for that object does not have any mandatory or assistive properties (it is identified only by its ordinal identifier, such as a Browser test object), then when you point to the object, the wizard is unable to fix the problem and displays a message that the object you pointed to has a test object description that is similar to the object that UFT could not identify.
Workaround: Use the Update from Application option in the Object Repository window (for objects in the local respiratory) or in the Object Repository Manager (for objects in a shared object repository) to fix the test object description.
|Updating a step by pointing to a different object class||
When the Maintenance Run Wizard cannot find an object in the application, and you point to a different object class to replace it, the Maintenance Run Wizard offers to add a step with that object and the object's default method. However, the wizard does not insert any method arguments for the step. If the step method has required arguments and you accept the step that the Maintenance Run Wizard proposes without modifying it, the step fails when you run it.
Workaround: Enter valid method arguments for the step.
|Updating XPath or CSS properties||
When running in Maintenance Mode, UFT may replace test objects with XPath or CSS identifier property values with new objects from your application.
Workaround: Use the Update from Application option in the Object Repository Manager to update specific test objects with XPath or CSS identifier property values.
|Objects used in function library||Maintenance Mode cannot fix problems in an object's properties, if the object is used in function library that is called by a step. If Maintenance Mode detects a problem in an object in a function library, a message is displayed indicating that the test is read-only and that Maintenance Mode is disabled.|
Update Run Mode
The Update Run mode does not update Insight test objects.
To update an Insight test object, open the object in the object repository, and click the Change Test Object Image button in the Test object image area.
|Checkpoints and output values||
Update Run does not support updating complex checkpoint and output value types such as File and XML.
During the Update Run, these checkpoints and output values run as they would in a regular run session and will fail if there are differences between expected and actual values.