Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    5
  • Subscribers subscribers
    26
  • Views views
    913
  • Users 0 members are here
Related
Options

UFT One cannot use xpath following-sibling

garecanbp

I need to create scripting to click the button next to one object. Due to the customer requested not to use Repo, I tried DP but the objects didn't have unique properties so I used the xpath.

the structure is like below:
<td> Row 1</td>
<td>
<input class=button></input>
</td>

The issue is I cannot use "following sibling" in UFT (I tested it in the browser and works but failed in UFT)
xpath 1: //td[title()='Row 1']/following-sibling::td//input[@class='button'] -> FAILED
xpath 2: (//td[title()='Row 1']/..//td//input[@class='button'])[1]-> SUCCESS

the xpath 2 is the workaround but tbh should be avoided because of the index. Could anyone suggest the cause UFT cannot use the sibling and give a good alternative for the xpath?

This case also applies to other siblings like "preceding-sibling" and "ancestor".

Tags:

Parents
  • 0  

    Hi,

    The "following sibling" or other siblings are supported in UFT One.

    I have tried the following code to verify the xpath.

    • HTML

    <!DOCTYPE html>
<html>
    <head>
        <title>Page title</title>
    </head>
    <body>
        <table>
            <td>Row 1</td>
            <td>
                <input class="button"></input>
            </td>
        </table>

    </body>
</html>

    • UFT script

    Browser("creationtime:=0").Page("micclass:=page").WebElement("xpath:=//td[text()='Row 1']/following-sibling::td//input[@class='button']").Highlight

    The `input object` can be highlighted successfully.

    Please run $x("your xpath description") in the browser console to check if it can find the right object.

  • 0 in reply to   

    hello, I run the xpath in the browser console before executing it in UFT.

    for the example:  //td[title()='Row 1']/following-sibling::td//input[@class='button'] 

    the xpath find the object in the browser console but it failed in UFT.

    For the same object in UFT, I have to use this xpath

    (//td[title()='Row 1']/..//td//input[@class='button'])[1]

  • 0   in reply to 

    Hi garecanbp

    Thanks for your feedback.

    Could you share more details about your application under test(such as a screenshot of the browser console when you try the XPath,  the DOM structure), the UFT version, the extension version, and the browser type?

    Alternatively, you can raise a ticket so that we can have a meeting with you to help you resolve the issue more quickly.

Reply
  • 0   in reply to 

    Hi garecanbp

    Thanks for your feedback.

    Could you share more details about your application under test(such as a screenshot of the browser console when you try the XPath,  the DOM structure), the UFT version, the extension version, and the browser type?

    Alternatively, you can raise a ticket so that we can have a meeting with you to help you resolve the issue more quickly.

Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.