· Defining xpath and css properties using Frame HTML tags is not supported. This may cause incorrect identification when identifying Frame objects or retrieving Frame objects using the ChildObjects method.
· Xpath and css properties are not supported for .NET Web Forms test objects or for other Web-based test objects that have .NET Web Forms parent test objects.
· When running in Maintenance Mode, UFT may replace test objects with XPath or CSS identifier property values with new objects from the 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.
Differences Between User-Defined XPath and Automatic XPath Behavior During Run Sessions
|Behavior in case of…||User-defined XPath||Automatic XPath|
|Multiple objects match the XPath value||UFT continues to identify the matching objects.||UFT ignores the learned XPath and continues with the regular object identification process.|
|No objects match the XPath value||Object identification fails, and UFT continues to identify the object using Smart Identification||UFT ignores the learned XPath and continues with the regular object identification process.|