:::: MENU ::::
Browsing posts in: Jenkins

CICD with Jenkins and HP ALM / Quality Center – Part 3

Some of our customers use HP Performance Center for load/stress testing. Instead of running performance at the end of the release and finding critical issues, these customers run HP Performance Center tests as a regular part of the development process via Jenkins. Bumblebee’s Jenkins plugin allows organizations to schedule, run, and report HP Performance Center tests and implement their desired CICD vision.

In this post, we will explain you can use Bumblebee Jenkins plugin to run HP Performance Center tests.

Part 3: Running HP Performance Center tests from Jenkins

To configure a Jenkins job to run HP Performance Center tests, add the Bumblebee HP PC Test Runner build step.

HP Performance Center produces test reports that can be published inside Jenkins builds. Bumblebee HP PC Test Runner task automatically downloads these reports from the HP Performance Center server and copies them to the specified Results Directory.

To publish these reports inside Jenkins, add the Archive Artifacts post-build step to job configuration and define appropriate values for Files to Archive

When the Jenkins job is triggered it starts a new run in HP Performance Center for the test specified by Path To Test and Test Set properties of the task. Once the HP PC test has started, Bumblebee HP PC Task waits for it to finish and checks the run’s possible Run States from time to time.

If a test has failed, Bumblebee marks the build as passed or failed based on the Fail Build If Task Fails job configuration property. If true, the build is marked as FAILED and build is aborted. If false, Bumblebee simply proceeds with the next test.

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

Sample execution log:

Bumblebee is very flexible and simple to setup. For a detailed step by step guide, please check out the latest Bumblebee docs


CICD with Jenkins and HP ALM / Quality Center – Part 2

If you are using HP ALM, chances are that there are significant amount of tests stored in ALM using a variety of HP Tools like UFT, LeanFT, etc. Instead of running HP tests via HP ALM and everything else via Jenkins and then trying to figure out what is failing in Jenkins vs. HP ALM, you can control everything via Jenkins while keeping things as in in HP ALM.

In this post, we will explain you can use Bumblebee Jenkins plugin to run existing HP Functional tests in ALM via Jenkins. The tests results will appear in both HP ALM and Jenkins.

Part 2: Running HP ALM Functional tests (UFT, LeanFT, etc) from Jenkins

To run ALM Testset from Jenkins, add Bumblebee HP ALM Test Set Runner build step to the Jenkins job configuration

When Jenkins build is executed, the Bumblebee HP ALM Test Set Runner step connects to HP ALM server and runs the specified ALM Testsets. The build waits till the test runs is completed in HP ALM.

Example: Jenkins build console

Once the build is complete, Bumblebee HP ALM Test Set Runner transforms the HP ALM test results in a JUnit report compliant schema so that it can be published within Jenkins, using the standard Publish JUnit test result report post-build step.

Bumblebee is very flexible and simple to setup. For a detailed step by step guide, please check out the latest Bumblebee docs


CICD with Jenkins and HP ALM / Quality Center – Part 1

In many organizations, Jenkins is used to build software, run unit tests, and run various kinds of testing frameworks. Example: Selenium, JUnit, Pytest, TestNG, Visual Studio Test, etc. These test metrics are very important and should be reflected in HP ALM to show the true health of any project. Bumblebee plugin for Jenkins allows users to integrate any testing framework with HP ALM without making any code changes or writing custom tools. In addition, the plugin allows you to run HP ALM tests directly from Jenkins. Many organization use Bumblebee and Jenkins to achieve CICD.

In these series of posts we will cover 3 main topics

  1. Exporting testing results from Jenkins to HP ALM
  2. Running HP ALM Functional tests (UFT, LeanFT, etc) from Jenkins
  3. Running HP Performance Center tests from Jenkins

1. Exporting testing results from Jenkins to HP ALM:

Integrating Jenkins with HP ALM is super simple by using Bumblebee’s plugin for Jenkins. Bumblebee’s Jenkins plugin allows you to Export test results to HP ALM and automatically create TestPlan, TestLabs, TestsSets, and TestRuns. This is extremely useful for running tests directly in Jenkins and automatically these test results in HP ALM.

Bumblebee Jenkins plugin can be installed via the Jenkins update center

Configure the Jenkins plugin global settings. manage Jenkins → Manage Jenkins → Configure System

Save Configuration to save your changes. Saving may take a few seconds because the Bumblebee plugin will validate the configuration before saving.

Bumblebee’s Jenkins plugin allows automatic export of Jenkins build’s test results to HP ALM. Bumblebee supports a variety of test results formats like JUnit, NUnit, testNG, Fitnesse, and Cucumber. To enable this feature, configure the Jenkins job and add Bumblebee HP ALM Uploader post-build step. In this step, configure a few fields and specify the results that need to be published.

Once the job is configured, simply build the job. The build console will show the Bumblebee Jenkins plugin to Bumblebee REST API activity. This output is quite useful for troubleshooting.

All the results will be processed by Bumblebee server and corresponding TestPlan, TestLab, Testset, and TestRun will be created automatically.

 

Bumblebee is very flexible and simple to setup. For a detailed step by step guide, please check out the latest Bumblebee docs