Use this dialog box to specify settings that
Silk Test Classic uses when it runs a script.
- Agent name
- Specifies the name of the agent on the target machine, that is, the machine on which you want to run a script or suite. Specify
a value only if you want to run your script on a machine other than the host machine.
- If you are testing applications across a network, select either
NetBIOS as the networking protocol to use. If you choose the Open Agent as the default agent, only TCP/IP is available.
- Default Agent
- Specifies which agent, the Classic Agent or the Open Agent, to use by default. For example, if your test cases target an
Apache Flex environment, specify the Open Agent as the default agent. For projects created prior to
Silk Test Classic 2008, the Classic Agent is selected by default. You can change the agent if necessary.
- Specifies the arguments, if any, that you want to pass to the script at runtime. Separate multiple arguments with spaces.
For example, suppose your script takes two arguments: the number of iterations to perform and the name of a test data file.
In this case, you would enter
- Use path
Specifies one or more paths along which
Silk Test Classic searches for include files. Include files can be named in the
Use files field or in a script’s use statement. If you specify a path,
Silk Test Classic searches the current directory and then each of the directories in the path named here. If you do not specify a search path,
Silk Test Classic searches the current directory only. The syntax for a path is the same as that used by the native operating system. By default,
Use path is set to
c:\Program Files\Silk\<SilkTest install directory>. Click
Browse to select an additional include path. The
Use path field contains a maximum of 1024 characters.
Silk Test Classic displays the first 256 characters of a directory. The 257th character is truncated.
- Use files
- Specifies the names of one or more include files for
Silk Test Classic to automatically load at startup. Do not specify files in this field if you intend to include a use statement for the files
in a script. Type the file names as you would type any other operating system path. You can use an absolute path or a relative
path. However, it is recommended that you use a relative path. For example, to include the Java SWT extensions for the Open
Agent, the relative path is
Browse to select an additional include file. The
Use files field contains a maximum of 1024 characters.
Silk Test Classic displays the first 256 characters of a directory. The 257th character is truncated. When you enable extensions or configure
Silk Test Classic adds an include file based on the technology or browser type that you enable to the
Use files box. For extensions that use the Open Agent,
Silk Test Classic names the include file
<technology_type>.inc. For instance, if you configure an
Apache Flex application, a file named
flex.inc is added. If you configure a Web application for a
Internet Explorer browser,
Silk Test Classic adds the
explorer.inc file. Extensions that use technologies on the Classic Agent are located in the directory
C:\Users\<Current user>\Documents\Silk Test Classic Projects\<Project name>\extend\. Technology domains that use the Open Agent are located in the directory
C:\Users\<Current user>\Documents\Silk Test Classic Projects\<Project name>\extend\<technology type>.
- Object filepath
- Specifies the location from which
Silk Test Classic reads and writes object files. Leave the field empty if you want to store object files in the same directory as their corresponding
source files, specify an absolute path if you want to store all object files in the same directory, or specify a relative
path if you want object files to be stored in a directory relative to the directory containing the source files.
- GUI targets
- Specifies the platforms for which you want to compile your scripts and include files (using conditional compilation). You
can specify as many GUI targets as you want; separate each GUI specifier with a comma. You use this field when doing distributed
testing with multiple platforms; if networking is disabled, then the field is ignored.
Silk Test Classic implicitly includes the local host GUI type.
- Default Browser
- Specifies the Web browser to use when testing Web applications. Make sure the extension with which you are testing appears
Default Browser field.
- Save object files during compilation
- Creates an object file from a script or include file when it is compiled. (An object file is always created for a script
or include file when it is saved.) The default is checked. Checking this option will minimize compilation time for features
such as Auto-Complete and Projects, which rely on frequent compilation.
To disable saving object files during compilation, the Auto-Complete options on the
General Options dialog box as well as this option need to be unchecked.
- Compiler constants
- Opens the
Compiler Constants dialog box, where you can define constants and assign values to them. You can use the defined constants in scripts and include
files anywhere you can specify an expression. Constants are evaluated and replaced with their values at compile time. To define
a constant, specify its name in the
Constant Name field and its value in the
Value field, then click
Add. You can edit or delete an existing constant by selecting it and clicking
- Specifies the name of the directory, or the name of the directory and file that stores the results of script runs.
Silk Test Classic always assigns the extension .res to all results files. If you supply a different extension,
Silk Test Classic will override it. If you leave the field empty (the default),
Silk Test Classic gives the results file the same name as the script and stores it in the same directory as the script. If you supply only
a directory name,
Silk Test Classic gives the results file the same name as the script and stores it in the directory you specify.
Note: If you provide a local or remote path in this field, the path cannot be validated until script execution time.
Silk Test Classic can only validate the path when the script is executing.
- History size
- Specifies an integer representing how many sets of results to keep for a script. Once this number is reached,
Silk Test Classic automatically deletes the oldest set of results each time it generates new results. A value of 0 saves all results files.
Default is 5.
- Write to disk after each line
- If checked, writes the results file to disk whenever the script generates output, as in the case of a print statement. Selecting
this option ensures that in the event of system failure,
Silk Test Classic will produce a results file containing output up to the time of system failure. The disadvantage of selecting this option
is that file I/O slows down script execution. By default, this check box is checked.
- Find Error stops at warning
- If checked, the
menu option locates error messages and warnings in results files. Otherwise, the command locates error messages only. By
default, this check box is checked.
- Show overall summary
- If checked, displays the summary of results for the entire script, suite, or test plan, including the start and elapsed time
of execution, and the total number of errors and warnings. By default, this check box is checked.
- Log elapsed time, thread, and machine for each output line
- If checked, records this information in the results file for each line that is written. Default is unchecked. To view this
information, make the results file active, then choose
Thread number, or
- Minimize while running
- If checked,
Silk Test Classic runs minimized while you run a script, suite, or test plan. By default, this check box is unchecked.
- Show detailed status window
- If checked,
Silk Test Classic displays the
Runtime Status window while you are running a script or suite when
Silk Test Classic is not minimized. By default, this check box is checked.
- Save status window position
Silk Test Classic remembers the position and size of the
Runtime Status window if you change it during script execution. The next time you run a script, the
Runtime Status window appears in the new position and/or the new size. Default is unchecked, in which case the
Runtime Status window always comes up in the same location and as the default size.
- Animated Run Mode (Slow-Motion)
- If checked,
Silk Test Classic waits one second after each interaction with the application under test is executed. Typically, you will only use this check
box if you want to watch the test case run. For instance, if you want to demonstrate a test case to someone else, you might
want to check this check box. You can set this check box in the
Run Testcase dialog box also, which enables you to enable or disable animated run mode each time you run a test case. When you enable
Animated Run Mode in the
Run Testcase dialog box,
Silk Test Classic makes the same change in the
Runtime Options dialog box. Likewise, when you enable or disable animated run mode in the
Runtime Options dialog box,
Silk Test Classic makes the same change in the
Run Testcase dialog box. Executions of the default base state and functions that include one of the following strings are not delayed:
- Print agent calls
- If checked, specifies whether or not you want the results file for each test run to include a list of all method calls made
by your script. Each entry includes the method name and the arguments passed to it. This is a useful feature for debugging
because it tells you exactly which methods were actually called by the running program. By default, this check box is unchecked.
- Print tags with agent calls
- If checked and
Print agent calls is also checked, includes tags with the method calls in your results files. By default, this check box is unchecked.