Bumblebee Jenkins plugin allows seamless integration of Jenkins jobs and build test results with HP ALM 10, 11, 12. The plugin processes jenkins build data and sends it to the Bumblebee server for processing. Bumblebee automatically creates TestPlan, TestLab, TestSet, and TestRuns in HP ALM.

Bumblebee plugin is ideal for organizations who want to reflect the data from Jenkins into their HP ALM project. Organization use Bumblebee to show unit tests, Selenium test, Visual Studio tests, and various other test frameworks that run in Jenkins into some HP ALM project. Bumblebee is a commercial product. For more details, please go to http://www.agiletestware.com/bumblebee


Why use Bumblebee plugin for HP ALM

The Bumblebee Jenkins plugin provides the ability to

Jenkins plugin Installation

Install the Bumblebee plugin for Jenkins using the Plugin manager. Please restart Jenkins after installing or upgrade the plugin.


The Bumblebee Jenkins plugin communicates with the Bumblebee web service which in turn communicates with HP ALM. You can download the Bumblebee server from the Agiletestware website

Detailed user guide for installing Bumblebee server.

Bumblebee Global Configuration

Configure the Bumblebee URL, HP ALM URL, username, and password.

Uploading test framework reports to HP ALM

Add the Bumblebee post build step in your job configuration. Specify ALM TestPlan and TestLab details. Bumblebee will automatically collect, parse, and insert test results in HP ALM.

Please refer to the documentation for details

HP ALM Results

Running HP ALM tests from Jenkins

Bumblebee's Jenkins build step allows you to run HP ALM TestSets directly from Jenkins and view the results in both Jenkins and HP ALM.

 Pre-Requisites for running HP ALM tests from Jenkins

To run test set from Jenkins you need to add Bumblebee HP ALM Test Set Runner build step to your build configuration


DomainThe name of HP ALM domain
ProjectThe name of HP ALM project
Test SetsA list of test sets to execute. Each test set path must start with new,line. Patch must start with Root and contains full path to the test set,in HP ALM TestLab. E.g. Root\folder1\testset1, where Root\folder1 is,TestLab folder and folder1 is the name of the test set to execute
Run ModeHow to run test sets. Possible values: LOCAL - run all tests on agent's,machine, SCHEDULED - run tests on planned host, REMOTE - run on remote,host
Run HostThe name of host on which tests shall be run. May be blank if Run Mode is LOCAL or SCHEDULED
JUnit Results DirectoryDirectory where JUnit-like execution reports will be placed. If it does not exist, Bumblebee will create it
TimeoutThe number of minutes to wait for test sets execution. 0 means wait indefinitely.

When Jenkins runs Bumblebee HP ALM Test Set Runner step it connects to HP ALM server and triggers specified test sets.

Here is an example of build log produced by Bumblebee:


Bumblebee HP ALM Test Set Runner puts results of test execution as a simple JUnit report which can be then published using Publish JUnit test result report step

Running local HP UFT tests directly in Jenkins

Bumblebee allows you to run local HP Unified Functional Testing tests directly from Jenkins and reports results back to Jenkins.


To override path to UFT Batch Runner, defined in the Global Configuration, you need to set a UFT_RUNNER environment variable on a Jenkins slave.

To set a value to UFT_RUNNER environment variable of Jenkins slave:

Adding and configuring "Bumblebee Local UFT Test Runner" build step

To add a new "Bumblebee Local UFT Test Runner" build step, just add a new build step in Jenkins build configuration with name "Bumblebee: Run local UFT tests".

"Bumblebee Local UFT Test Runner" build step has the following configuration parameters:

Note: If you use .mtb file from GIT repository, you need to make sure paths to tests are correct and point to tests in build directory. You can use windows batch script for this.

Bumblebee UFT step puts results of test execution as a simple JUnit report into folder defined by "Results Directory".
These reports can be then published using Publish JUnit test result report Post-build step.
Please note that it shall be configured to scan the output directory of Bumblebee UFT task.

When Jenkins runs Bumblebee UFT step, it will trigger local HP UFT Batch runner and record its output:

Checking build report

 Bumblebee UFT step captures results of test execution and produces a simple JUnit report which are then attached to the build report and can be seen on "Test Results" page:

For failed tests, report contains an error message reported by UFT:

UFT also produces detailed reports with description of all steps, screenshots, etc...
You can setup Jenkins to capture those results as build artifacts and attach them to a build results.
To do that, you just need to add "Archive artifacts" Post-build step to your build configuration and define appropriate value for "Files to archive".

After build has finished, artifacts are displayed on "Artifacts" tab:

Running HP Performance Tests from Jenkins

HP Performance Center is a powerful set of tools for composing and running performance tests which is used by many companies.

Bumblebee offers Jenkins users ability to easy trigger Performance Center tests and report results back to Jenkins.

When the task starts it triggers a new test run in PC and then polls run status from time to time. When run reaches some terminal state or timeout is reached then task is finished.

Terminal states are:

If run finished successfully, all test results are downloaded into specified folder in the build working directory.


Global configuration

To start working with the new task the following Bumblebee Global Settings should be set:

Adding and configuring of "Bumblebee HP PC Test Runner" task

To add a new "Bumblebee HP PC Test Runner" build step, just add a new build step in Jenkins build configuration with name "Bumblebee HP PC Test Runner".

"Bumblebee HP PC Test Runner" build step has the following configuration parameters:

Parameter nameDescription
DomainDomain name in HP ALM.
ProjectProject name in HP ALM.
Results DirectoryDirectory to which test result files will be saved.
Path To TestPath to a test in HP ALM TestPlan, e.g. "Subject\folder1\test", where "Subject\folder" is a path to a test folder and "test" is the name of a test to run.
Test SetPath to a test set in HP ALM TestLab, containing correspondent test instance, e.g. "Root\folder1\testSet", where "Root\folder1" is a path to a test lab folder and "testSet" is the name of a test set. If test set does not exist or test is not assigned to it, Bumblebee task will try to create a new test set and assign a test to it.
Post Run ActionDefines what PC should do after a test run. Available options: Collate And Analyze, Collate Results and Do Not Collate.
Time Slot DurationTime to allot for the test (PC parameter). It cannot be less than 30 minutes (limitation by PC).
Use VUD LicensesIf true, the test consumes Virtual User Day (VUD) licenses.
TimeoutOverrides a global PC timeout value and represents the number of minutes to wait for the Performance Center test to finish. 0 means wait indefinitely.
Retry AttemptsNumber of retry attempts, before task completely fails.
Retry IntervalNumber of seconds to wait between retry attempts.
Interval Increase FactorIncrease factor for retry interval. E.g. if it is set to 2, then each subsequent wait interval between attempts will be twice bigger than the previous one.
Polling IntervalThe number of minutes between two test state requests.
Fail Build If Task FailsIf true and task has failed (or timeout has reached), then the whole build will be failed. If false, then build will not be failed even if task has failed.

Attaching PC results as Jenkins build artifacts

Since, Performance Center produces some test reports, Bumblebee task downloads them from the PC server and stores into Results Directory, defined in a build configuration.

To see those reports on Jenkins build page, they need to be attached as build artifact, so before running the build, Jenkins should be configured to capture and archive required artifacts.

To do that, you just need to add "Archive artifacts" Post-build step to your build configuration and define appropriate value for "Files to archive".

Running the task

When task is triggered it starts a new run in HP Performance Center for a test specified by "Path To Test" and "Test Set" properties of the task. The following parameters affect test execution in PC:

Please refer to HP Performance Center documentation for detailed description of these parameters.

After test is started, task waits for it to finish and polls run state from time to time ("Polling Interval"). If test reaches one of the following states, Bumblebee assumes that test has passed:

If test reaches one of the following states or timeout has occurred, Bumblebee treats test as failed:

If test has failed Bumblebee makes a decision on whether build shall be failed or not based of value of "Fail Build If Task Fails" property. If it is true, then the whole build is failed. If it is false, then Jenkins does not fail and proceeds with the next task.

If an error occurs during fetching runs status from PC, Bumblebee will try to retry failed action according to the retry settings defined for a task.

Here is an example of the execution log:

Pulling test results from HP ALM

If you want to pull test results from Jenkins and display them as JUnit report of your build, you can use "Bumblebee: Import HP ALM Test Results" step.


Configure Import HP ALM Test Results step

Parameter nameDescription
DomainDomain name in HP ALM
ProjectProject name in HP ALM
LoginUser name in HP ALM. If it is set, it will override global settings
PasswordPassword in HP ALM. If it is set, it will override global settings
Results DirectoryPath to the directory where to put JUnit-like reports containing results of tests in HP ALM
Test Set PathPath to a TestSet in HP ALM TestLab to pull results from it


During the execution of "Bumblebee: Import HP ALM Test Results" test step, Bumblebee searches for a Test Set by path given in "Test Set Path" parameter, creates JUnit XML report file and puts it into "Results Directory" folder. This folder can be used by JUnit publisher to build test trends.


Version 4.1.4 (released September, 2019)

Version 4.1.3 (released July, 2019)

Version 4.1.2 (released February, 2019)

Version 4.1.1 (released January, 2019)

Version 4.1.0 (released April, 2018)

Version 4.0.9 (released February, 2018)

Version 4.0.8 (released October, 2017)

Version 4.0.7 (released September, 2017)

Version 4.0.6 (released July, 2017)

Version 4.0.5 (released June, 2017)

Version 4.0.4 (released August, 2016)

Version 4.0.3 (released July, 2016)

Version 4.0.2 (released July, 2016)

Version 4.0.1 (released February, 2016)

Version 4.0.0 (released October, 2015)

Version 3.0.2 (released November, 2014)

Version 3.0.0 (released November, 2014)