The Silk Performer BDLT error 'BrowserClick(BrowserEngine: 29 - UI element not found)', can be reported for a number of reasons. Below are some of the possible reasons and solutions. 1. The UI element reported as not found is really not there. This could be caused by a dynamic value in the locator string or a server problem. If the locator string has a dynamic value, use a wild card or a different locator. You can configure the recorder to use a different locator as described here . 2. The UI element is slow to appear. Use BrowserVerifyProperty or BrowserFind to get the correct locator once its available. 3. There was a change in method of how browser clicks are performed in Silk Performer 9.5 which might lead to the above error being reported. The replay engine now uses Windows API-level events instead of JavaScript events for some functions. For a small number of applications this causes problems. The details of this change are included in the 9.5 release notes section 'Next-Generation Browser-Driven Web Load Testing' along with a 'legacy' setting to turn off the change. To do this go to Settings | Active Profile | Web (browser-driven) and check the 'Legacy Input Mode' checkbox 4. The locator might have 2 'functional controls' in one locator. The locator spy will see these as a single locator and wont be able to click on the 2 controls independently. It is possible to use exact coordinates to click on a certain part of the locator, for instance over to the right where a browse button might be. This can be achieved using the nX and nY parameters of the BrowserNativeClick function. We can see this behaviour with the 'Browse' button in http://demo.borland.com/samples/explorer.html#fileupload. However drilling down into the DOM we can also use the locator //BUTTON[@textContents='Browse...']. In most cases, it is better to try and use the locator but if necessary coordinates are a fallback option.
↧