Consider the following when you are working with data-driven test cases:
4Test Editor contains additional menu selections and toolbars for you to use.
Silk Test Classic can data drive only one test case at a time.
- You cannot duplicate test case names. Data-driven test cases in the same script must have unique names.
- The Classic 4Test editor is not available with data-driven test cases in
- You cannot create data-driven test cases from test cases in
.inc files; you can only create data-driven test cases from test cases in
.g.t files. However, you can open a project, add the
*.inc, select the test case from the test case folder of the project, and then select data drive.
- When you data drive a
[use '<script>.t'] is added to the data-driven test case. This is the link to the
.t file where the test case originated. If you add a test case from another script file then another use line pointing to that
file is added. If the script file is in the same directory as the
<script.g.t>, then no path is given, otherwise, the absolute path is added to the use line. If this path changes, it is up to you to correct
Silk Test Classic will not automatically update the path.
- When you open a
.g.t file using
Silk Test Classic automatically loads the data source information for that file. If you are in a
.g.t file and that file’s data source is edited, click
to refresh the information from the data source.
- If you add a new data-driven test case to an existing
.g.t file that is fully collapsed,
Silk Test Classic expands the previous test case, but does not edit it.