Load testing with silkperformer: An overview

Recording Script for Web application:

1. Click Model Script on the workflow bar. The Workflow – Model Script dialog box appears.
2. Select one of the listed browsers from the Application Profile list, depending on the browser you want to use for recording.
3. In the URL field, enter the URL that is to be recorded.
4. Click Start recording. The Silk Performer Recorder dialog opens in minimized form, and the client application starts.
5. To see a report of the actions that happen during recording, maximize the Recorder dialog by clicking the Change GUI size button. The maximized Recorder opens at the Actions page.
6. Using the client application, conduct the kind of interaction with the target server that you want to simulate in your test. The interaction is captured and recorded by the Recorder. A report of your actions and of the data downloaded appears on the Actions page.
7. To end recording, click the Stop Recording button. The test script is generated from the recorded traffic.
8. In the ensuing dialog, name your test script and specify where to save it. In the Silk Performer Recorder message that appears, confirm that you want to close the Recorder.

Customize user data:

• Without user-input data customization, all simulated transactions are identical and do not account for the variables that are typically experienced in real world environments.
• For example, you can customize the user-input data that is entered into forms during testing using the Parameter Wizard. The Parameter Wizard lets you specify the values that are to be entered into form fields during testing. This enables test scripts to be more realistic by replacing recorded user-input data with randomized, parameterized user data.

Customize Session handling:

This task explains the process of creating a parameter based on a random variable.

1. Click Customize User Data on the workflow bar. The Workflow – Customize User Data dialog box opens.
2. Click the Customize user input data in HTML forms link. TrueLog Explorer then performs the following actions:
3. Selects the first WebPageSubmit API call node in the menu tree.
4. Opens the Step through TrueLog dialog box (with the Form submissions option button selected).
5. Displays Post Data view
6. Post Data view shows the page that contains the HTML form that was submitted by the selected WebPageSubmit call. The submitted form’s controls are highlighted; a green border around a control indicates that the submitted value is the same as the initial value (and was not changed by the user during recording). A red border indicates that the submitted value differs from the initial value (and was altered during recording). When your cursor passes over a form control, a tool tip shows the control’s name in addition to its initial and submitted values; an orange line indicates the corresponding BDL form field declaration in Form Data view below.