This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Not able to run UFT edge browser script from ALM

We have recently updated our UFT scripts from IE browser to EDGE browser .

If we run the script for the test case, the script works fine , but if we run the same script from ALM , it is not getting executed .

Version of UFT -  15.0.2

Version of Edge - Version 105.0.1343.42

Note: Previously for IE browser , we could run the same script from both UFT and ALM without any issue .

Can someone please help

  • 0

    Anyone else facing this issue. 

    Would be really great if someone can help

  • 0   in reply to 

    Could you share more details? What do you see in automatic runner after you click Run? Is UFT triggered at all?

    You may want to try running a test without edge involved and see if it is in general a UFT/ALM integration issue or really an edge browser script issue

  • 0 in reply to   

    Yes UFT is triggered. I able to previously run my script for IE browser .
    For IE integration with ALM it works fine, but if I open ALM in Edge and also try to run my Edge browser script, the script fails because the index of browser gets changed .
    I haven't encountered this issue when executing for IE

  • 0   in reply to 

    It appears you already identified the issue. :)

    I would suggest using other properties than index to locate the browser, that should resolve the issue.

  • 0 in reply to   

    The index of the browser get auto captured when we add the browser in the object repository and this is one of the properties along with the several others that gets captured ,
    Also as we have multiple modules and scripts already created , changing the index will take very long for us ,
    I am looking for some other solution .
    I was also wondering as Edge and ALM integration is very common why is no one else facing this issue . 

  • 0   in reply to 

    Index is never a good property to use, it is something you need to seriously consider to change to avoid issues like this.

    I guess it is not that no one encountered a similar issue, just that such identification issue is quite straight forward and a change in the properties used is most likely necessary.