LoadRunner Cloud (previously named StormRunner Load) is a product under constant development with multiple releases every year. With each new release comes new or updated functionality, which means that many customers simply do not notice what is new or what has been improved, hence this series of blog posts.
The following features are the focus of this blog post:
- Project Management
- Exporting raw transactions data
- Adding Vusers during a test run
- Monitoring Windows resources on On-premises Load Generators (OPLGs)
- Sharing data files between multiple scripts
A new LoadRunner Cloud tenant is by default a single project where all users have access to all assets and licenses.What some customers don't know is that LoadRunner Cloud (LRC) can handle multiple projects on the same tenant, each with its separate users, licenses and OPLGs.
This makes it easier for larger organizations, or simply those with many ongoing performance testing projects, to structure their testing in a more organized way. Assets, such as scripts, tests and monitors, are not shared between projects, although OPLGs and licenses can be shared between projects if required.
This makes it easy to ensure that important projects always have access to the needed resources and aren’t blocked by other projects, e.g. by assigning certain LGs and parts of the tenant license to that project only.
Note: A support ticket is required to enable Project Management, and once enabled it cannot be disabled.
Exporting Raw Transactions Data
For those customers who would like to do their own data mining and analysis using the raw transactions data, it is possible to export that data from LoadRunner Cloud as a CSV file.
On the General tab of the load test setup, tick the Store transactions raw data box before running the test.
Run the load test as normal and once concluded, export the data to a CSV file.
A download link will then be available in the Notifications area.
The downloaded results can then be opened in either e.g. Excel or a suitable text editor.
Adding Vusers During a Test Run
Running performance tests in LoadRunner Cloud against a new AUT means that we are not always sure about exactly how many Vusers are needed in order to hit our targets. Fortunately, we have the ability to add more Vusers during run-time, but we do have to enable that before we start the test. This is done by ticking the Enable adding Vusers during a test run box on the General tab of the Load Test.
Then enter, in a percentage, how many additional Vusers that we would like to be able to add during the test run.
Once the test is running and any initial ramp-up has finished, the Change Load button will be enabled in the top right corner.
The Change Load window will be populated with the current number of running Vusers and a new value can be entered and applied.
The added Vusers will be ramped-up according to the previous pace, and once finished, it will again be possible to add more Vusers if there are any left.
Monitoring Windows Resources on OPLGs.
When running a performance test utilizing cloud LGs, LoadRunner Cloud will automatically assign a suitable number of load generators to the test. But when running using on-premises load generators, the testers themselves will need to decide on how many OPLGs are needed. In order to make sure that the OPLGs aren’t overloaded, it is possible to view the Windows resource monitor graphs from the OPLGs in a running test. The graphs are available in the new Dashboard under the Monitors metric and has the standard Window Resource counters available.
By viewing these during a running test, it’s easy to tell if an adjustment is needed to the number of OPLGs. In a case where any of the monitored resources are consistently above 85% utilization, that would often indicate that either too many Vusers are running on the OPLG, or that the Think Time or Pacing of the Vusers would need to be increased.
Note: A support ticket is required to include Windows OPLGs in the available monitors.
Sharing Data Files Between Multiple Scripts
Normally with Vugen scripts, if any parameter- or other data-files are used by the scripts, they needed to be included in the zipped script file. With the introduction of data files, we can now keep those files separate and accessible from multiple scripts, which then is especially useful if that data changes. Simply upload an updated data file, instead of updating all the scripts separately.
Data files support a number of different file-formats and will be accessible on the script’s current path. As an example, we can create a parameter file in a Vugen script and then move that .dat file out from the script directory and zip it up separately. Upload the script as normal and upload the data file into Assets -> Data Files.
We can see the contents of the zip-file under the File Structure tab, and later on, which scripts are using the data file under the Details tab.
To assign a data file to the scripts, done under the Scripts tab, by selecting the scripts and clicking the Data file button and selecting the required data file.
While the load test is running, the selected scripts will pick their parameter data from the assigned Data File.
That's it for now, please check back for further blogs if you enjoyed reading this.