To create or edit a
Silk Test Classic test:
-
In the menu, click
.
-
Select a container or folder node in the
Tests tree where you want to insert a new test, or select the test that you want to edit.
-
Click
(New Child Test) on the toolbar, or click
(Edit).
The
New Test/Edit Test dialog box appears.
-
Type a name and description for the test.
Note: Silk Central supports HTML formatting and cutting and pasting of HTML content for
Description fields.
-
If you are creating a new test, select
Silk Test Classic Test from the
Type list box. To import multiple
Silk Test Classic test cases at the same time, select
Silk Test Classic Multi-testcase import. Click
Next.
TheTest Properties - Select Test Script dialog box appears.
-
Click
Browse and select the test script file from either the defined
Silk Test Classic project or the source control directory.
The test script, with file extension
.t or
.g.t, is defined relative to the test container’s root node in the source control profile. For example
/<Silk Test Classic project>/MyScript.t.
-
Click
Next.
The
Test Properties - Select Testcase dialog box appears.
Note: If the
Silk Test Classic script is a data-driven
.g.t file, for example
SilkTestScript1.g.t, then data sources are completely controlled within the script file and not through the data-driven properties of
Silk Central. The
Data-driven check box is checked by default when you use a data-driven script file. For more information about data-driven
Silk Test Classic tests, refer to the
Silk Test Classic documentation.
-
Select a test case from the available test cases in the defined script file or specify a custom test case. When the custom
test case field is already populated, the
Silk Test Classic test was automatically created, using the export functionality within
Silk Test Classic. When you use the custom field to specify the test case, you can terminate the test case name with a parenthesis "()". Inside
the parenthesis, you can specify test data, including parameters. Specifying data in the custom field will override the values
of the
Test data property.
-
Optional: Type additional execution arguments into the
Test data field.
These arguments are processed by
Silk Test Classic during the execution of the test. If several arguments are passed to
Silk Test Classic, they have to be separated by a comma (,). If a
String argument is passed to
Silk Test Classic, the argument must be set in quotation marks (“). When test data is more complex, we recommend that you use parameters in
the test data, for example
${ParameterName}. Parameters are replaced automatically within test executions.
Note: This field has a maximum length of 2000 characters.
-
Define whether the test should provide a TrueLog.
Tip: When running your tests with the Open Agent, this setting must be turned on both in
Silk Central and in
Silk Test, otherwise no TrueLog will be provided. Default execution mode for data-driven tests is plan-based. When you use script-based
execution mode for a data driven test, change the
DataDrivenScriptMode setting in the
Silk Test Classic element of
SccExecServerBootConf.xml. For more information, refer to the
Silk Test Classic documentation.
-
If required, specify an option set file. By default,
Silk Central closes all open
Silk Test Classic option set files. To specify an option set file, specify the file name relative to the test container’s root node in the
source control profile.
-
Click
Finish to create the
Silk Test Classic test.
Note: If you possess
Silk Test Classic test cases that require more than one hour to complete, adjust the time-out settings for
Silk Central. Otherwise,
Silk Central assumes an error has occurred and terminates the execution. For details about time-out settings, see the
Administration topics in this Help.