Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

StormRunner Load version 3.2: Adding more integrations for stronger DevOps tool chain

Kristina_Avrio Super Contributor.
Super Contributor.
1 0 2,332

Micro Focus StormRunner Load version 3.2 is available now. With this release, we are building on the tool’s open architecture by introducing new integrations and enhancing existing ones, so you can make performance testing an integral part of your CI/CD practice.

With version 3.2, we are introducing the integrations with Team Foundation Server (TFS, also known as Azure DevOps Server) and Visual Studio Team Services (VSTS and also known as Azure DevOps),  which are tools that cover the entire application lifecycle and supports the DevOps process. StormRunner Load tests can be triggered from TFS and VSTS as part of a build script and basic test results are fetched back into the tools'  CI server’s interface.

srl 1.png

We announced the integration of StormRunner Load with Selenium back in version 2.5, yet with StormRunner Load 3.2 we are enhancing the integration by introducing support for the Mocha Framework in addition to the existing JUnit framework support.

Knowing how much you rely on Jenkins for automating your builds, we are continuously making improvements on the plugin so you can continuously deliver software at a faster pace and with lower risk. The most recent Jenkins enhancement will assure that when a job is terminated, the StormRunner Load test that has been running as part of the job will stop and all available results up to this point will be downloaded.

Continuing to make StormRunner Load simple to use, we are now introducing an easy way to manage the on premise Load Generators (OPLGs).  In previous versions, users had to remove an OPLG from all tests before it could be deleted from an assets list, but now they can easily delete or remove the OPLGs from the assets list with a click of a button. Users can delete a load generator when they have a single project or simply remove a load generator from a project when they work with multiple projects. Notifications are also getting easier to manage. When there is an important message or a temporary system issues (technical problems from a given cloud region, for example), SaaS operators can simply push the messages and the notification icon will alert the users.

srl2.png

Lastly, in the new Analysis module, we now show where your transaction is compared to the SLAs, and the area in which the SLA is violated will be covered in red for easy and immediate visualization. At the same time the configuration pane will indicate transactions with SLA breaches and a new BREAK column will show the percentage of transactions that are over the threshold. In addition, Bulk operation will enable you to select a metric and show or hide all its sub-metrics by type.

srl3.png

That’s all for this release. Till the next one. And if you have not tried StormRunner Load yet, you can give it a go by signing for the free 30 day trial.

The StormRunner Load Team 

Tags (2)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.