DevWeb runtime settings

The DevWeb runtime settings pages enable you to configure runtime behavior for DevWeb scripts.

In this topic:

About DevWeb runtime settings

DevWeb has a dedicated runtime settings UI. To view it, when your DevWeb script is open, select Replay > Runtime Settings.

The runtime setting views include descriptions of the settings. Hover over a field to see the description at the bottom of the page. Additional information on some of the DevWeb runtime settings is given below.

You can configure the DevWeb runtime settings manually, by editing the rts.yml file for the script. For details, see the LoadRunner Developer and DevWeb Help Center.

DevWeb runtime settings views:

DevWeb Settings

Enables you to configure and customize general runtime settings for DevWeb scripts. These include sections for the following:

  • Log. Includes log mode and log level.

  • Proxy. Includes PAC support, proxy server details and authentication credentials, authentication type (basic or NTLM), and excluded hosts.

  • Replay. Includes snapshots on replay or error, and Dynatrace AppMon monitoring (see Dynatrace AppMon integration).
  • HTTP. Includes keep alive and connection timeouts.
  • SSL. Includes disabling HTTP/2, ignoring bad certificates, and TLS version.
  • Encryption. Data encryption key location.
  • VTS Proxy. Includes information for VTS proxy server connection.
Run Logic Enables you to define run logic for actions. For details, see Configure run logic.
Pacing Enables you to define timing between iterations. The pace tells the Vuser how long to wait between iterations of your actions.
Think Time Enables you to define think time options, to control how the Vuser uses think time during script execution. Think time defines for how long the Vuser will pause its execution at the point where think time is used. This is to emulate a user pausing before moving on to the next step in a business process.
Additional Attributes

Enables you to provide additional user arguments for the DevWeb script. By adding the arguments in this view, you can pass external parameters that can be used within the script.

You specify the name and value for each command line argument. They are added to the rts.yml file for the script, and they can be retrieved at a later point during the test run using load.config.user.args.

Additional Log Settings

(Available in Controller.) Enable the collection of additional logs when the script is running in a scenario. The logs provide data that can help to troubleshoot issues.

This field is disabled by default; to conserve resources, enable only when needed.

Note: This functionality is available from version 2022 R1.

Back to top

Configure run logic

In the Run Logic view, you can define the order and frequency for running script actions during a test. Not all actions that are defined in the script need to be included, so you can build the run logic for the test run without changing the actual code.

Using the run logic tree structure, you can add multiple actions, group the actions into blocks, and define the logic for how the blocks are run.

Tip: Check out the video: Define run logic for DevWeb scripts.

When an item in the tree is selected, you can right-click and use the context menu for each item to insert, delete, and move items as relevant, as well as use cut, copy, and paste functions.

Unnamed actions: Unnamed (anonymous) actions do not have a name argument supplied in the action definition in the script, and they cannot be added to the run logic. A warning message is displayed if your script contains unnamed actions. If you want to these actions to be included, add name arguments for them in the script

The Run Logic view includes the options and functions described below:

UI element Description
Number of iterations The number of times the entire run block (within the run logic tree) will be repeated during the test run. When you change the value in the field, it also changes the number next to the run block.
Enable run logic during replay

Use the check box to toggle the run logic on or off. When selected, the defined run logic order is used when executing the script.

Note: If run logic is not enabled, the actions in the script are run in the same order that they are loaded by the JavaScript parser. This is similar to, but not identical to, their order in the script code.
Automatic fill Use the button to automatically populate the run logic tree with all the all non-anonymous actions in the script. This overwrites the current tree configuration.
Insert

Enables you to add items to the tree:

  1. Select a block or action in the tree.

  2. Click Insert. Select an item from the displayed dropdown list.

    The list contains the actions are relevant for the selected block, and Block if it is permitted to add a block at that location in the tree.
Delete Immediately deletes the currently selected item, and all child items.
Move Up/Move Down Moves the selected item up or down within its block.
initialize block

This is a predefined block that is executed once only, at the beginning of the test. It is mostly used for initial business processes such as enter domain and login page.

You cannot define child blocks for the initialize block, and included actions always run sequentially.
run block

This is a predefined block that controls the run logic for the main business process that you want to test. The run block can contain multiple actions, and multiple blocks of actions.

It can be run multiple times, according to the number of iterations that you set at the top of the view. This number is indicated to the left of the block name:

finalize block

This is a predefined block that is executed once only, at the end of the test. It can be used for business processes such as logout.

You cannot define child blocks for the initialize block, and included actions always run sequentially.
<Block run logic>

You can define the logic used to run each block of actions within the run block:

Sequential All items in the block run in the order they appear (default).
Random An item in the block is picked at random each run of the block, and only that item (action or block) is executed. The probability for an item being picked is weighted by its run percentage (see Run percentage, below).
Shuffle Run all items in the block, but in a random order.

Number of loops

The number of times to run each block. Click on the number in the circle to change the value.
Run percentage

The percentage of times to run this item, within a block that is set to use random run logic.

Random run logic requires a percentage probability value for each item in the block, so that the total probability for all items adds up to 100%. Items with a higher probability will be picked more often. Any item with 0% will not participate in the run.

By default, the percentage values are divided evenly between the items. Click on a percentage to change the value.

If the total percentages do not add up to 100%, the block is shown in error. In this situation, when you save the runtime settings, the percentage for the first item in the block is automatically adjusted so that the total is 100%.

If you change the run logic from Random to another logic, your changes to the default percentage values are not saved. If you reset to Random, the default percentages are used.

Back to top

Dynatrace AppMon integration

DevWeb data can be pushed to the Dynatrace AppMon monitor on the AUT server during the test run, enabling correlation of the web server data collected by the Dynatrace agents with the data provided by the DevWeb tests. When the integration is enabled, an additional header (x-dynaTrace header) is added to each web request.

Dynatrace AppMon requires that a transaction be associated with each web request. If there are multiple transactions, then by default VuGen associates the transaction that has the latest start time. The transaction name is used to display the web request in the Dynatrace AppMon dashlets.

To enable the integration, in the DevWeb Settings view select the check box for Enable Dynatrace AppMon monitoring.

Back to top

See also: