-
Click
File in the menu and click
New Project. In the tree, click
GUI-Level Testing and
Silk Test. Enter a
Name and a
Description and click
Next.
-
In the
File field, specify the
Silk Test asset you want to use for a performance test.
Silk Performer automatically detects the file type and enables the appropriate button below.
-
Click
Import Keyword-Driven test.
-
In the
Tests area, select the keyword-driven tests you want to import.
-
Specify the
Import Options:
- Ignore parameters: Does not include any of the parameters that are part of the keyword-driven test.
- Script parameters as static strings: The parameters are directly added to the script, which means that they are static strings within the script.
- Script parameters as values from CSV file: The parameters are stored within a .csv file and referenced in the script. The .csv file is added to the project and displays
within the
Project tree.
-
Specify the
Row selection order:
- Random: Adds the BDL function
FileGetRndRow to the script.
- Sequential - machine-wide: Adds the BDL function
FileGetNextRow to the script.
- Sequential - test-wide: Adds the BDL function
FileGetNextUniqueRow to the script.
-
Select a
Web Browser from the drop-down list. This list is only enabled when the file that is to be imported is based on a
Silk Test web project.
Silk Test web projects can make use of the single-session concept for GUI-level testing.
-
Enable
Use project attributes for session login to let
Silk Performer use credentials from the
Project Attributes to login into sessions. To edit the project attributes, click
. The credentials will be added to the
TInit transaction of your script. The check box
Use project attributes for session login is only available when the file that is to be imported is based on a
Silk Test web project.
Silk Test web projects can make use of the single-session concept for GUI-level testing.
-
Click
OK and save the .bdf file.
Silk Performer imports the test assets and generates an appropriate .bdl stub.