Scripts

Scripts contain the actions of a business process and form the backbone of your performance test. Your test definition can contain one or multiple scripts.

In this topic:

Back to top

Manage scripts

You manage your scripts in one of the following places:

• Assets > Scripts tab

• Load tests > Load profile pane

Use the Assets area to manage scripts globally in the LoadRunner Cloud repository, and make them available to all tests in your project.

Use the Load tests area to manage scripts for a specific test, without affecting the global script asset.

Back to top

Reload scripts

In the Assets > Script area, you can reload scripts to make sure that your test is using its latest version.

You can reload a script from the file system or from a Git repository. You can reload an existing script from Git, even if it was originally uploaded from the file system.

To reload a script from another file on the file system:

1. Click .

2. If a Git agent is connected to the project, expand the Reload dropdown and click Reload.

To reload a script from a Git repository:

1. Make sure a valid Git agent is connected to the project. For details see Add and manage scripts in a Git repository.
2. Expand the Reload dropdown and click Reload from Git.
3. In the Reload script from Git dialog box, select an agent, repository and branch.
4. Select the script you want to reload. Only select one script.
5. Select Auto sync to instruct LoadRunner Cloud to keep the script up to date from the Git repository.
6. Click Reload.

Manage runtime settings

After you click Reload in the previous section's Reload script from Git dialog box, the Reload script dialog box opens. To manage the runtime settings, select an option:

• Do not keep runtime settings. Instructs the reload not to keep the existing script's runtime settings. Instead, it uses the new script's runtime settings.

• Keep runtime settings. Instructs the reload to keep the existing script's runtime settings and not use those included with the new script.

• Include Run Logic. Retains the Run Logic customizations of the existing script. If you do not select this option, when you reload a new script, the Run Logic properties of the new script are used.

Runtime setting scenarios

Scenario 1

• The existing and new scripts are of the same type and Keep runtime settings and Include Run Logic are both selected. Result: All runtime settings are kept as they were in the existing script, including the runtime settings mode—global or local.

Scenario 2

• The existing and new scripts are of the same type and Do not keep runtime settings is selected. Result: All runtime settings are updated from the new script. The run logic is reset to the default value, local.

Scenario 3

• The existing and new scripts are of different types. Result: The Do not keep runtime settings and Keep runtime settings are ignored and all runtime settings are reset to their defaults from the new script. The runtime settings modeis reset to the default value, local.

Back to top

View script details

In the Script Details pane within the Assets > Script area, you can learn more about the selected script. This expandable pane is located to the right of the grid. It displays additional information about the script and a list of tests and data files associated with the script.

Script Details pane

The Script Details pane, only available when a single script is selected, displays the following information:

Section	Description
Summary	Displays general information about the script, such as script type, by whom and when the script was created, and by whom and when the script was modified.
Git	If the script was uploaded from a Git repository, the pane displays general information about the relevant repository and branch. Click Commit history to view details of the last 10 commits on the script. Note: The Commit history link is displayed only for scripts that were uploaded or synced with the LoadRunner Cloud Git agent version 3.7 or later. The commit history description displays only the first 100 characters for each included commit.
Related tests	Displays all load tests that use this script.
Related data files	Displays all data files used by this script.

Back to top

Upload Silk Performer scripts

To use Silk Performer scripts in your load test, you need to upload them through the Silk Performer Workbench.

To upload Silk Performer scripts:

1. In the Silk Performer Workbench window, select File > Upload Project to > LoadRunner Cloud.

2. In the Login step, enter the tenant and login information.

3. In the Project step, select the LoadRunner Cloud project into which to upload the script.

4. In the User Types page, select the user types to upload. Click Finish.

   

For details on working with Silk Performer, see the Silk Performer Help Center.

Back to top

Add and manage scripts in a Git repository

You can connect to an existing Git script repository and add those scripts to your LoadRunner Cloud load tests.

For details, see Git integration.

Do the following to add or update scripts from your Git repository to LoadRunner Cloud:

Action	How to
Access the Git repository	Click and select Upload from Git to open the Git repository dialog box. Note: For shared Git agents, if multiple users upload or synchronize scripts using the same agent simultaneously, the uploading or synchronizing time increases.
Select an agent	From the dropdown menus, select the agent, repository, and branch that connect to the script repository you want to use. For details on managing your Git agents, see LoadRunner Cloud agents. If you want all the scripts that are uploaded from the repository to be configured for auto sync, select the Auto Sync check box. You can also individually configure scripts for auto sync. For details, see Sync Git scripts.
Select a script	Select one or more scripts from the Git repository. Click Add.
Sync Git scripts	You can sync Git scripts both manually and automatically. To sync Git scripts manually: Toggle the Show Git scripts only switch. Select the scripts you want to sync. Click to sync your scripts with the Git repository. Note: When you manually sync a Git script, runtime settings configured for the script in LoadRunner Cloud are retained. To sync Git scripts automatically: Toggle the Auto sync switch for the scripts you want to be synced automatically. When a change to a script is made in the repository and the script is automatically updated in LoadRunner Cloud, a message is added in the notifications area in LoadRunner Cloud. Note: When you automatically sync a Git script, the runtime settings configured for the script in LoadRunner Cloud are retained.

Back to top

Edit and view scripts in LoadRunner Cloud

You can edit or view the script's files in a text editor from within LoadRunner Cloud.

The following guidelines apply to the editor and viewer:

• Editing is supported for all script types with the exception of TruClient, Selenium JUnit, and JMeter.
• .NET scripts can only be viewed—not edited.
• The editor/viewer can show up to five levels in the script's folder structure.
• The editor/viewer may not display files that are humanly unreadable or exceedingly large.
• Changes to Git scripts are not retained if you perform a sync.

To view and edit the contents of a script:

1. In the Load Tests tab, choose a test.
2. Click to open the load test's Load profile page.
3. Select the check box of the script that you want to edit. You can only make one selection at a time.
4. Click .
5. In the left pane of the Edit script window, select the script file you want to view or edit.
6. Click a page thumbnail in the right pane to scroll to the section of the script that interests you.

7. View or edit the script.

   Tip: Auto-completion is supported for DevWeb scripts.

8. Click Save to save your changes. Your changes are saved globally—all tests that use this script are affected. The Details pane shows the modification date and time.

Back to top

Assign labels

Use labels to help you organize scripts in your repository, or to organize your load tests in the Load tests and Results pages. The labels you create are common to both scripts and load tests.

Labels can be nested in sub-categories:

The expandable labels pane is located to the left of the grid. Click the left or right double arrows at the top to show or hide the pane.

You can perform the following actions for labels:

Action	How to
Create a label	In the Labels pane, click Create label to open the New label dialog box. Give the label a name. Optionally, nest the label under another label. Click to select a label color.
Edit a label	From the Labels pane, highlight a label. Click the vertical ellipsis and select Edit.
Delete a label	From the Labels pane, highlight a label. Click the vertical ellipsis and select Remove. Removing a label also removes any sub-labels.
Assign a color to the label	From the Labels pane, highlight a label. Click the vertical ellipsis and select Color.
Add a sub-label	From the Labels pane, highlight a label. Click the vertical ellipsis and select Add sub-label.
Manually assign a label	You can assign a label to a script manually after the script has been uploaded. In the Assets > Scripts grid, select the check box of the scripts you want to label. For Results or Load tests, select one item in the grid. Expand the (Assign labels) drop down. Select one or more labels to assign to the selected items. Use the Search box to find a label name.
Automatically assign a label	You can assign a label to a script automatically when uploading the script. To assign a label to a script automatically, select the required label before uploading the script's .zip file or before dragging and dropping the script into the Assets > Scripts page. Note: To assign a label to a script uploaded from a Git repository, you must use Git agent 2022.10 or later.
Filter by a label	You can filter scripts, load tests, and results by a specific label. In the Labels pane, highlight a label or sub-label to filter the displayed items. Use the Search box to find a label name.

Back to top

Assign a script key

A script key contains an encryption key for an encrypted DevWeb script. By assigning a script key to a script, you can run the script without having to expose the encryption key within the script itself.

You create and manage script keys in Assets > Script Keys. For details, see Script keys. When assigning script keys, you can also create a new key by clicking Create a key.

To assign a script key to a DevWeb script, select the script and click . Select the script key you want to assign and click OK. The name of the assigned script key appears in the right pane as part of the summary script information.

To remove an assigned key, select the script, click and then click Clear and OK.

Back to top

Assign data files

A data file contains information used by scripts. By assigning a data file to multiple scripts, you can manage the data in one location rather than having to update multiple scripts for each change.

You can assign multiple data files to a script. Save the data files in zip format, as described in Prepare data files.

Before assigning data files to scripts, upload the files to LoadRunner Cloud from the Assets > Data Files tab. For details, see Upload and manage data files.

To assign data files to scripts:

1. Open the Scripts page from one of the following tabs:

   • Click Assets > Scripts.

   • Click Load tests, select a load test, and click Load profile.

2. Select a script and click . The Assign data file(s) to scripts dialog box opens. By default, you can assign up to five data files to a script.

   Note: To view Git data files only, select the Show git data files only check box.

3. Select the data files to assign to the selected script and click OK.

4. To remove a data file assignment, repeat step 2, and clear the check box for that data file.

Back to top

See also:

• Data files
• Define a load test