How do the new features in SilkPerformer 2008 improve the testing of Remedy Web ARS?
Silk Performer 2008 new features allow easier customization and understanding of scripts recorded against the Remedy web client by eliminating the need to customize length prefixes and introducing names to individual data items.
Take for example the following Postdata:
In order to customize the input value "NewCityWithoutRules03" we would need to consider each of the points below:
The function "WebRemedyBackChannelUrl" includes the use of web forms to handle this data. The data captured in the various WebRemedyBackChannelUrl functions is the raw data being communicated between the client and server and is often done via AJAX type methods. What Silk Performer now does is map the raw data into an XML representation in the web form as shown below:
As we can see from this screenshot, the Remedy data is represented in XML format which not only eliminates the need for all the length prefixes, but also provides string names for the individual data items. In the case above, it is much easier to identify for example, the current server or current schema in the XML than it is in the raw data. By the same token, if we want to customize the value GetEntryList, we can do so directly in the XML attribute without having to worry about modifying any of the length or array attributes to compensate for the change.
For further details and examples please see the Silk Performer 2008 on-line Help section entitled Remedy.