Modeling GUI-Level Tests - Keyword-driven

  1. 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.
  2. 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.
  3. Click Import Keyword-Driven test.
  4. In the Tests area, select the keyword-driven tests you want to import.
  5. 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.
  6. 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.
  7. 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.
  8. 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 Project > Project Attributes . The credentials will be added to the TInit transaction of your script.
    Note: Silk Test web projects can make use of the single-session concept for GUI-level testing, thus login credentials are not required at all. Nevertheless, for further script customization it might be useful to enable Use project attributes for session login.
  9. Click OK and save the .bdf file.
Silk Performer imports the test assets and generates an appropriate .bdl stub.