There is a known issue within Silk Performer 16.5 that is applicable to both Web Business Transaction (HTML/HTTP) and Web Browser Driven projects and relates to the exclusion of a section of the URL in a WebPageUrl (http) and BrowserNavigate (AJAX) call during replay. If a url includes a '#' tag and a standardhost has been specified within SILK PERFORMER | SETTINGS | ACTIVE PROFILE | WEB (PROTOCOL LEVEL) | HOSTS, the section of the URL after the '#' tag is excluded from replay. For example, as opposed to http://demo.borland.com/testsite/common_main.asp#URL Encoding being used during replay, the following url will be used - http://demo.borland.com/testsite/common_main.asp . Generally the section of the URL after a '#' tag would refer to a location on the same page, therefore in essence a WebPageUrl and BrowserNavigate call, with its subsequent functions should still work. However we have seen applications that use a # tag to indicate a different page. Thus if the incorrect page is accessed (due to the exclusion of part of the url) during replay, this of course will lead to subsequent failings within the script, be it WebPageLink or BrowserClick functions. R&D are currently aware of this issue and hope to introduce a fix within an up and coming Silk Performer release. In the meantime, a workaround would be to avoid the use of a standardhost, if different pages within the application are referenced via a '#' tag.
↧