Setting Browser-Recording Options

  1. In Silk Performer, expand the Profiles node in the Project tree.
  2. Right-click the profile that you want to configure and choose Edit Profile.
    Tip: Alternatively, you can choose Settings > Active Profile from the menu bar.

    The Profile - [<profile name>] dialog box opens, and the Replay category is displayed in the shortcut list on the left.

  3. In the shortcut list on the left, click the Record button. The Record category is displayed.
  4. In the shortcut list, click the Web (Protocol Level) icon.
    Note: For mobile Web application testing, you can select an alternative user agent string (for example, iPhone, iPad, Android, Windows Phone, or Blackberry) on the Browser tab.
  5. Click the Recording tab.
  6. Use the Browser emulation level area to specify the level at which you want Web traffic to be recorded for use in your test scripts.
    • Click the Page-level Web API (HTML / HTTP) option button to record Web traffic at the browser level. When you choose this option the Silk Performer Recorder generates scripts that call functions provided by the page-level web API.
    • Click the Low-level Web API (HTTP) option button to record Web traffic at the browser level. When you choose this option the Recorder generates scripts that call functions provided by the low-level web API.
    • Click the TCP/IP-level API (TCP/IP / HTTP) option button to record Web traffic on the TCP/IP level. Select this option to capture proprietary protocols carried by HTTP.
  7. Select an Advanced context management level from the list box. You can disable advanced context management, customize the individual settings, or choose one of the presets Level 1, Level 2 (default) or Level 3.

    These options are only available when the Browser emulation level is set to Page-level Web API (HTML / HTTP).

    • Click the View Settings button to view or customize the level of advanced context management.
  8. Check the Automatic page detection check box to enable the recorder's page-notation technology. When you use the page-level Web functions, this feature attaches embedded documents that are loaded by JavaScript code into a Web page. When you use the low-level functions, all the requests that load a web page are wrapped by WebUrlBeginPage and WebUrlEndPage function calls and so automatically creates page timers and synchronizes the downloading of Web pages for improved accuracy.
  9. Check the Convert URL query strings to forms check box to convert recorded URL query strings to Web forms and then include the forms in the dclform section of the generated test script. Disable this option only if the URLs are irregular.
  10. Check the Enable persistent-cookie recording for returning-user simulation check box to have the recorder generate a WebCookieSet function call at the beginning of the current transaction for each persistent cookie that you receive from the Web server. When your script is run, each WebCookieSet function then emulates a cookie that is persistently stored in the virtual user’s cookie database.
    Note: WebCookieSet function calls are marked as comments, so you must remove the comment marks to activate the function calls.
  11. Check the Encapsulate concurrent pages using timers check box to encapsulate concurrent pages with timers. Page timers, normally included in the page-level web functions or in calls of the function WebUrlBeginPage, are not scripted. Instead, functions MeasureStart and MeasureStop are inserted automatically (based on timings). A series of browser activities is considered "concurrent" if there is no browser-idle period longer than the value of the minimum recorded thinktime.
  12. Use the Record additional HTTP headers area to specify additional HTTP headers you want to record, such as those generated by a custom HTTP client.
  13. Click the Add button to add the name of an additional HTTP header you want to record, such as one generated by a custom HTTP client. You must know the exact name of the header you want to record to use this feature. The HTTP Headers dialog box opens.
    1. Enter the name of the header you want to add to the list, or select one from the list box.
    2. Click OK.
  14. Click the Edit button if you want to edit the name of a selected HTTP header. The HTTP Headers dialog appears.
    1. Edit the header name as required.
    2. Click OK.
  15. Click the Remove button if you want to remove a selected additional HTTP header from the list.
    1. Click Yes to confirm the deletion.
  16. Click OK to save your settings.
Parent topic: Web (Protocol Level) Settings