Run TruWeb scripts

You can run a TruWeb script using the TruWeb executable, or in LoadRunner, Performance Center, or StormRunner Load.

TruWeb executable

To run a TruWeb script, run the relevant command:

Run mode Command and description
single

TruWeb <path to script folder>

Runs a single iteration for a single Vuser, regardless of the supplied scenario.yml file.

This is the default mode.

load

TruWeb -mode=load <script folder>

Runs the script using the scenario settings defined in script's the scenario.yml file. For more information, see scenario.yml. Responsible for the TruWeb scenario settings when running a TruWeb script in load mode. For details, see Run TruWeb scripts..

Example:  

Windows

Single mode: TruWeb C:\ScriptFolder

Load mode: TruWeb -mode=load C:\ScriptFolder

Linux/MacOS

Single mode: TruWeb ~/ScriptFolder

Load mode: TruWeb -mode=load ~/ScriptFolder

Viewing test logs and results

  • Test run logs per Vuser are saved to ..\<Script folder>\results\logs. The log filename contains the Vuser ID.

    The log files are generated according to the vuserLogger settings in the script's rts.yml file.

  • Raw data is saved to a SQLite database file, truWebDB.db, in ..\<Script Directory>\results\.

    Note: If you use DB Browser for SQLite to view the raw data (recommended), make sure to close the file before running another test. If left open, DB Browser may lock the database file for write access.

Back to top

Database tables

The raw data generated when you run your TruWeb script is saved to a SQLite database file, in ..\<Script Directory>\results\truWebDB.db.

The database creates the following tables for the script run:

Table Description
ActiveVusers

Provides a count of total running Vusers executing code within iterations. The number decreases when Vusers are waiting between iterations (pacing), and increases again when they enter the next iteration.

An entry is added to the table every time the total number changes.

AtomicTransaction

Provides time measurements per request/response pair (URL).

This data is not reported by default, due to the performance override. To active it, in the runtime settings file (rts.yml), under the httpConnection section, change reportAtomicTransactions to true.

BytesSent Provides the amount of bytes sent to the server (upload) per request, per Vuser.
Connections
(from version 2018.11.4)
Provides for each Vuser information about opened and closed connections (state connect or shutdown).
CustomDataPoints

Provides values for user-defined data points, reported through load.utils.reportDataPoint API, per Vuser.

Hits Provides information about each request, including HTTP status code, per Vuser.
RunningVusers

Provides a cumulative count of running Vusers. An entry is added to the table every time the total number changes.

Throughput

Provides the amount of bytes received from the server (download) per response, per Vuser.

Transactions

Provides information on status and duration for each transaction reported, per Vuser.

Back to top

External tools and IDEs

You can run your TruWeb script from the TruWeb plugin within your scripting tool.

Example: JetBrains WebStorm (IntelliJ)

Select Tools > External Tools > Run TruWeb.

The results are displayed in the bottom panel. To run the script again, click the green Run button.

Example: Atom.io

To run one iteration of the script with one user, select TruWeb > Run single user.

To run a scenario with the script, select TruWeb > Run scenario. TruWeb runs the script using the scenario defined in the scenario.yml file.

TruWeb in Micro Focus testing tools

You can run a TruWeb script using LoadRunner, Performance Center, or StormRunner Load (see supported versions). Multiple TruWeb scripts can be run in parallel on one load generator.

To run a TruWeb script in your Micro Focus testing tool:

  1. Prerequisite for LoadRunner/Performance Center: If your script was created in a tool other than VuGen, import the script into VuGen:

    1. In VuGen, select File > Open > Import TruWeb Script.
    2. Browse to your script's main.js file and click Open.
    3. Enter a name for your script, and the location where you want to save the imported script.
    4. Click Import.
  2. In your testing tool, run your script as you would any other script. For more information, see the relevant Help Center for your testing tool.

See also: