-
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
Silk4J test.
-
In the
File field, specify the archive that is to be tested.
The archive is automatically added to the profile classpath. The available classes are then retrieved and displayed, sorted
alphabetically in the
Class field.
-
From the
Class list, select one of the available classes for testing.
When you do not specify a specific archive for testing, the wizard enables you to specify a class that is available in the
profile classpath. Type the fully qualified class name into the
Class field, for example
java.lang.String.
The available constructors and methods are automatically retrieved and displayed.
-
In the
Methods area, select the methods that you want to call.
-
To filter the methods that are shown in the
Methods area, perform the following steps:
-
Click the
Advanced Settings button (the funnel icon above the
Methods area).
-
Once you have customized filter settings, click
OK to update the
Methods area.
-
To change general Java settings including the Java version, Java home directory, or JVM DLL, click the
Active Profile Settings link.
The
Profile Settings dialog opens to the
Java/General page for Java projects (JUnit project type).
Note: Changes made to these settings (for example Java Classpath) may lead to different results. Selections made in the
Class,
Constructor, and
Methods fields will be updated with the new results.
Note: If you change the Java version, Java home directory, or JVM DLL, you must restart
Silk Performer for the changes to take effect.
-
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.
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.
-
Click
OK and save the .bdf file.
Silk Performer imports the test assets and generates an appropriate .bdl stub.