Configuring Browser-Driven Replay Settings

  1. In the Projects tree menu, right-click the Profiles node and select Edit Active Profile. The Profile - [Profile1] - Simulation dialog box opens at the Simulation tab.
  2. Click the Replay category button.
  3. Scroll down to and select Web (Browser Driven). The Web (Browser Driven) / General tab displays.
  4. Select the browser you want to use for this settings profile from the list.
  5. Use the Simulation group box to set options for realistic simulation of users visiting Web sites:
    • Click the First time user option button to generate a realistic simulation of users who visit a Web site for the first time.

      Persistent connections will be closed, the Web browser emulation will be reset, and the document cache, the document history, the cookie database, the authentication databases, and the SSL context cache will be cleared after each transaction. In such instances, Silk Performer downloads the complete sites from the server, including all files.

    • Click the Revisiting user option button to generate a realistic simulation of users who revisit a Web site. Non-persistent sessions will be closed, but the document history, the persistent cookie database, and the context cache will not be cleared after each transaction. In such cases, pages are not downloaded if they exist in the document cache.

    • Select the IE Compatibility Mode to define the rendering mode that Internet Explorer (IE) uses to display automatic replaying on the user's Web browser. The Default value depends on the user's Internet Explorer browser version.
    Note: Simulation settings are not applied when replaying your script with the Browser Application. However, all caching settings that you configure within Internet Explorer's Internet options will be applied to your browser-driven tests.
  6. Select a replay compatibility to define how locators are generated. Setting this option ensures flawless replay of older scripts with newer versions of Silk Performer and therefor helps to avoid compatibility issues. You can also define the replay behavior for every single script by manually scripting the BrowserReplayCompatibility function.
  7. Ensure that the Legacy input mode setting is disabled.
  8. Click the Synchronization tab.
  9. Configure Synchronization settings as required.
    • The Synchronization mode option configures the algorithm that is used to wait for the ready state of a browser invoke call (pre and post invocation).
    • The Synchronization timeout option configures the maximum time in milliseconds that is used to wait for an object to be ready (pre and post invocation).
    • In the URLs to exclude from synchronization text box, type the entire URL or a fragment of the URL for any service or Web page that you want to exclude. Some AJAX frameworks or browser applications use special HTTP requests, which are permanently open in order to retrieve asynchronous data from the server. These requests may let the synchronization hang until the specified synchronization timeout expires. To prevent this situation, either use the HTML synchronization mode or specify the URL of the problematic request here. Separate multiple entries with a comma.
    • The Object resolve timeout option configures the maximum time in milliseconds to wait for an object to be resolved during replay.
    • The Object resolve retry interval option configures the time in milliseconds after which another replay attempt should be made following an object not resolving.
  10. Click OK.