BlazeMeter Plugin to TeamCity

BlazeMeter has released a new plugin to TeamCity to simplify your load testing needs.You only need to connect your BlazeMeter account to TeamCity, configure a simple build step and you are good to go. You can configure TeamCity to run the BlazeMeter build step whenever you want, and the test will start with your pre-configured settings.

What is TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers and build engineers working on .NET, Java, and Ruby projects. JetBrains TeamCity is a user-friendly continuous integration (CI) server for professional developers and build engineers.

 

How to install BlazeMeter’s plugin for Teamcity ?

  1. Download the TeamCity (JetBrains) plugin.  or  Clone BlazeMeter's TeamCity plugin fromGitHub and compile. Compilation instruction are available in the README file.
  2. Copy the 'BlazeMeter.zip' file to the 'TeamCity Data Folder/plugins' directory, and restart the TeamCity server and agents.
 

How to configure BlazeMeter’s plugin for TeamCity ?

  1. First, configure the BlazeMeter user key. You can get this key from your BlazeMeter user profile.
  2. The user key configuration page is accessible from the ‘Administration’ page in the ‘BlazeMeter’ link under ‘Integration’.
  3. This is also the place to configure your proxy server settings: Name, Port, User and Password.
 

How to configure a build using BlazeMeter’s plugin for TeamCity ?

  1. Add a new build step with type 'BlazeMeter'.
  2. If your keys were pre-configured in the global settings, you will now see all your tests in the drop down. Select a test to run.
  3. Enter the thresholds for the error percentage and response time, to specify when a build becomes unstable or fails.
  4. Choose the test duration.
  5. You can also opt to select a data folder to upload your files in order to mask the test with new parameters.
  6. The Data folder: files from this folder will be uploaded to BlazeMeter.
  7. Make sure to ‘Save’ your settings.

Paths can be:

  • Absolute path (ex': in Windows: C:/Test/DataFolder, in Linux: /mnt/share/datafolder)
  • Relative path. This is relative to checkout directory. ex': DataFolder , this assumes that your checkout structure contains the DataFolder in the main node.

Please Note, if you choose to upload the files, be sure to fill in the field ‘Main JMX’ with the  ‘.jmx’  file name in the Data Folder.

Want to learn more about running performance testing within CI/CD? Watch our on-demand recording, How to Scale Test Automation with Jenkins & JMeter

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.