Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Forum Post: BrowserClick(BrowserEngine: 29 - UI element not found)

$
0
0
Having an issue with this error.  This is in TM ART 4.2, SP1.  I do have a ticket with BMC open, but others working with the application are experiencing the same issues and it seems to be an issue with how the lines for the script are handled.  The lines in question are below. BrowserDlgSetButton("Message from webpage #1", "OK"); BrowserClick("//A[@textContents='Remove']", BUTTON_Left); BrowserDlgStop(); This is the order in which they were recorded.  Playback is fine, no errors at all, but when the script is deployed it fails on the last line.  The process is, click through the screens to add an item to a shopping cart.  At the end of the test, the item is removed from the shopping cart by clicking remove.  When this is performed, an external window is generated requesting an Ok or Cancel.  From what I understand of the BDL scripting, the call for the Ok before the actual click of Remove is by design to store the attribute to use when the window is provided.  Is there something that can be added to click and verify the link in one fail swoop or is this what should be happening?  To me, it seems that it's trying to validate the Remove link AFTER the fact, but I don't know.  I can provide execution logs, but trying to get some ideas to think of ways to correct this issue.

Viewing all articles
Browse latest Browse all 4084

Trending Articles