Setting GUI-Level Testing 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, click the GUI-Level Testing icon. On the Session page, the Session settings area is used to configure the connection between your console session and remote desktop sessions.
  4. Check the Run Try Script on console check box to have Silk Performer run a Try Script on the console application. When this option is enabled, you can view what Silk Performer does during tests, but you are limited in what you can do on your computer because Silk Test uses your console. If disabled, Try Scripts will connect to and run Silk Test on remote desktop sessions.
  5. Check the Allow usage of console session on agents check box if you do not have a terminal-server license for all agents, or if your agents run on Windows Home or Windows Professional editions. Silk Performer only uses this option if the connection to a terminal services session fails, or if no user credentials are provided.
    Note: When this option is selected, you can start only one virtual user on each agent (for agents that have no Terminal Server license and Windows Home/Professional systems).
  6. Define a Connection timeout (in seconds) to specify how long Silk Performer should wait before a connection is established to remote desktops. Set this setting to 0 to have no timeout.
  7. Select a Color Depth setting. The Color Depth setting enables you to specify the color depth of terminal server sessions that are used by virtual users to drive applications via Silk Test. You can select from 8 bit (256 colors) up to 32 bit (true color).
    Note: Color depth settings defined using the BDL function StInitSession override profile settings configured here. When the optional uColorDepth parameter is omitted, profile settings are used.

    The server may limit maximum color depth. The client can not force a color depth setting that is higher than is supported by the server. Please see Terminal Services Configuration documentation for details about your server version's color-depth limitations.

  8. Complete the Username/Password settings to enable automatic login if you only require a single set of login credentials. These credentials will be automatically loaded into the StInitSession function. These credentials can be overruled by scripted settings, for example, by providing parameters to the StInitSession function using project attributes.
  9. On the Execution page, the Execution Settings area enables you to configure settings for the script and the runtime. Check the Log Silk Test errors check box to have errors and warnings that are sent back by Silk Test logged as informational warnings (this option is enabled by default).
  10. Select a TrueLog setting for the remote desktop session from the Generate TrueLog file for list box:
    • Select None (the default) to not have TrueLog written.
    • Select On Error to have TrueLog written only when errors are encountered.
    • Select Custom when you wish to have TrueLog written based on your custom settings.
    If you select Custom TrueLog settings, your TrueLog settings will be read from the Silk Test option file, or they can be set via the StSetOption function.
    Note: Even if you select OnError or Custom from the TrueLog on SilkTest list box, Silk Test will only write TrueLog files if you also specify in Silk Performer’s settings that TrueLog should be written. To do this, click the Generate TrueLog Files button or the Generate TrueLog On Error Files button on Silk Performer’s toolbar.
  11. Select a Screenshot mode:
    • None: Captures no screens.
    • Active Window: Captures the active window of the test application.
    • Active Application: Captures the test application and any other window within the test application.
    • Desktop: Captures the entire desktop.
    Note: This list box is just enabled for UFT Developer (Silk4J) and UFT Developer (Silk4NET) projects. It sets the screenshot mode used for the TrueLog file. This setting applies only to successful playback steps. If playback steps fail, the entire desktop is captured.
  12. Specify an Execution timeout (in seconds) to specify how long the runtime should wait before test cases execute. Set this setting to 0 to have no timeout.
  13. Results history size (set to 9 by default) specifies how many test-case results Silk Test can save in a .res file.
    Note: By starting a new test, the results in the .res file are reset.
  14. In the Silk Test Classicoption file field, browse to and select a Silk Test Classic option file. Refer to Silk Test Help for full details about option files.
    Note: This field is just enabled for Silk Test Classic projects.
  15. Click OK to save your settings.
Note: When a GUI-level monitor is deployed on a Silk Test Agent with Terminal Services installed, Silk Performer automatically looks up the RDP port used for Terminal Server session creation.