New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Micro Focus Expert
Micro Focus Expert
2386 views

Git integration in StormRunner - managing your testing scripts in Git

Git integration in StormRunner - managing your testing scripts in Git

(the post was written by Wei Sun and Lynn Liu from the StormRunner Load R&D team)

As a performance engineer, you could have many testing scripts for various projects you are working on. To efficiently manage your testing artifacts, you need a version control system like Git, SVN etc. The distributed nature of Git is a perfect fit to the Agile testing nowadays. It allows users to be more flexible in how they collaborate on projects.

In recent StormRunner 2.2 release, Git integration was introduced to allow you to connect your Git repository to your StormRunner tenant, not only from your internally hosted Git repository, also GitHub, GitLab and Atlassian Stash (Bitbucket). Using the integration, you can directly upload your scripts to StormRunner from your Git repository. If the scripts had been updated in your Git repository, you can easily synchronize the changes by one click.

Here we use a small example to demonstrate how the Git integration simplifies your script management. The demonstration will show you how to seamlessly sync the script between Vugen and StormRunner. More about ‘VuGen now connects you to Git repository’ 

  1. Configure StormRunner Git Agent, connect it to your tenant. See how to configure the StormRunner Git Agent.
  • Start the Git Agent Configuration tool to specify the URL of your repository.
  • Git agent needs read-only permission to your repository.
  • The supported URL prefixes are: HTTP, HTTPS.

1.png

  • If the repository is private, enter your credentials by clicking Advanced.

2.png

  • Click Retrieve to get branches from your repository.
  • You can run multiple Git agents (even on the same machine) to use multiple repositories or branches.
  • If the agent is connected, its status is displayed as ‘Connected’ in StormRunner. And Upload from Git option for scripts will be enabled.

3.png 4.png

23.png  

  1. Choose Upload from Git. Click Add to upload selected scripts via your Git agent.

6.png

  • Another feature in StormRunner is ‘Label’. You can use the cool functionality to manage your test scripts easily.21.png

     

  1. Vugen Git integration
  • Start Vugen, go to Version Control -> Git Options -> Import from remote repository. It will clone the remote repository to the local path.

8.png

    • Start ‘DotNet1’ project from local repository and modify the script as you want. Save the changes locally and then commit your changes to remote repository.
    • Note you could configure git ignore list or untrack file to reduce the size of your script.22.png  
  • The change on comment & modified time indicates that the ‘DotNet1’ script had been updated in the repository.

10.png

  • Now, we can synchronize the ‘DotNet1’ script in StormRunner via clicking Sync selected.

24.png

  • After syncing, ‘DotNet1’ script has been updated accordingly.

12.png

  • Now you can run load test with the updated script.

That’s it! We urge you to try out this new capability to see how it will help you shorten your scripting and uploading process. Try it out

2 Replies
Micro Focus Expert
Micro Focus Expert

Nice article.

0 Likes
Highlighted
Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

Hello MicroFocus Team,

 

Quick question: Can we integrate LoadRunner 12.5 with GIT repository ?

 

Thanks

0 Likes
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.