When replaying SilkPerformer Protocol Level scripts, for complex Web applications, there is often a lot of dynamic data (for session information) which requires customization for successful replay. The first step should always be to use the TrueLog Explorer ‘Customize Session Handling Wizard’ to see if SilkPerformer can automatically customize the required session information: If the ‘Customize Session Handling Wizard’ cannot automatically customize the required session information, then manual customization would be the next step. By performing two identical recordings (clearing cache and cookies before each), this could in theory provide two identical scripts. When the scripts are not identical, anything which is changing is dynamic and may need customized for successful replay. After doing so, a tool such as CompareIT can be used to identify changes. To re-cap, the following would be the correct series of steps to identify dynamic data within the script: • Clear Browser Cache and Cookies • Perform a recording of the Web Application • Again clear Browser Cache and Cookies • Perform another (identical) recording of the Web Application • Open the two resulting scripts in a tool, such as CompareIT, and identify any changes (dynamic data) You can then search the TrueLog for any of this dynamic data, which occurs in the ‘In Data / Body’, parse the data, and provide the variable in place of the hard coded data in the script. i.e. • Open the TrueLog, Use CTRL+F (or EDIT | FIND) and search for the dynamic value • When found, highlight the data, right click and select ‘Parse Selected Text into a Variable’ • Replace the hardcoded value, in the script, with the variable you have now created Note that if the dynamic data you are searching for appears in the ‘Out’ tabs, then this indicates that the value is generated by something Client Side such as JavaScript. Handling Client Side JavaScript with SilkPerformer Protocol Level recordings is quite complex. For this reason, you may want to consider the SilkPerformer Browser Driven Approach which runs an instance of a Browser, rather than sending data at the Protocol Level. This not only allows Client Side JavaScript to run, but also handles session information via the Browser instance, removing the need to customize dynamic data as outlined in this article. 2814913
↧