The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Bumblebee HP ALM Plugin

View this plugin on the Plugins site

step([$class: 'AddTestToSetStep']): Bumblebee: Add Test to Test Set

  • domain : String
    HP ALM Domain
  • project : String
    HP ALM Project name
  • testPlanPath : String
    Path to a test or test folder in HP ALM which shall be added to a test set
  • testSetPath : String
    Path to a test set in HP ALM into which test(s) shall be added

step([$class: 'BumblebeePublisher']): Bumblebee HP ALM Uploader

  • configs
      Array / List of Nested Object
    • domain : String
    • projectName : String
    • testPlan : String
    • testLab : String
    • testSet : String
    • format : String
    • resultPattern : String
    • customProperties : String
    • failIfUploadFailed : boolean
    • offline : boolean
    • defectCreatePolicy : String
    • defectCreateStatus : String
    • defectSeverity : String
    • defectReopenStatus : String
    • defectResolvePolicy : String
    • defectResolveStatus : String
    • defectCreateProperties : String
    • defectReopenProperties : String
    • defectResolveProperties : String

step([$class: 'GetTestResults']): Bumblebee: Import HP ALM Test Results

  • domain : String
    HP ALM Domain
  • project : String
    HP ALM Project name
  • resultsDir : String
    Path to the directory where to put JUnit-like reports containing results of tests in HP ALM.
    This path can be used for publishing JUnit reports in subsequent post-build action.
  • configurations
      Array / List of Nested Object
    • testSetPath : String
  • user : String (optional)
    HP ALM Login Name. If set, this value overrides value from Bumblebee Global Configuration.
    If empty, value from Bumblebee Global Configuration will be used
  • password : String (optional)
    HP ALM user's password. If set, this value overrides the value from Bumblebee Global Configuration.
    If empty, value from Bumblebee Global Configuration will be used

step([$class: 'RunPcTestBuildStep']): Bumblebee HP PC Test Runner

  • almPassword : String (optional)
    HP ALM user's password. If set, this value overrides the value from Bumblebee Global Configuration.
    If empty, value from Bumblebee Global Configuration will be used
  • almUser : String (optional)
    HP ALM user. If set, this value overrides the value from Bumblebee Global Configuration.
    If empty, value from Bumblebee Global Configuration will be used
  • domain : String (optional)
    HP ALM Domain.
  • failIfTaskFails : boolean (optional)
    If task shall fail the build in case it fails.
  • outputDir : String (optional)
    Directory where Performance Center reports will be placed. Relative to the workspace root. If it does not exist, it will be created.
  • pollingInterval : int (optional)
    Test status polling interval in seconds.
  • postRunActionString : String (optional)
    Performance Center Post Run Action.
  • project : String (optional)
    HP ALM Project name.
  • retryCollateAndAnalysisAttempts : int (optional)
    Defines how many times it will retry Collate or Analyze phase if they failed, before task completely fails.
  • retryCollateAndAnalysisFlag : boolean (optional)
  • retryCollateAndAnalysisInterval : int (optional)
    Number of seconds to wait between retry attempts.
  • retryCount : int (optional)
    Number of retry attempts, before task completely fails.
  • retryInterval : int (optional)
    Number of seconds to wait between retry attempts.
  • retryIntervalMultiplier : double (optional)
    Increase 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.
  • testLabPath : String (optional)
    Path to a test set in HP ALM TestLab. Must start with Root\, e.g. Root\folder1\testSet1, where Root\folder1 is a path to test lab folder and testSet1 is the name of a test set. Test set will be created if it does not exist.
  • testPlanPath : String (optional)
    Path to a test in HP ALM TestPlan. Must start with Subject\, e.g. Subject\folder1\test1, where Subject\folder1 is a path to test folder and test1 is the name of a test.
  • timeout : int (optional)
    The number of minutes to wait for the Performance Center test to finish. 0 means wait indefinitely.
  • timeslotDuration : int (optional)
    Time Slot Duration in minutes.
  • vudsMode : boolean (optional)
    If true, the test consumes Virtual User Day (VUD) licenses.

step([$class: 'RunTestSetBuildStep']): Bumblebee HP ALM Test Set Runner

  • domain : String
    HP ALM Domain
  • project : String
    HP ALM Project name
  • runMode : String
    Where to run test sets: locally, on scheduled host or remotely
  • host : String
    Host on which test sets will be executed
  • testSets : String
    A list of test set paths to be executed. Each test set starts from a new line. Example: Root\Release\2.0
  • outputDirPath : String
    Path to the directory where to put JUnit-like execution results. Basedir of the fileset is the workspace root. If directory does not exist, it will be created
  • timeOut : int
    The number of minutes to wait for test sets execution. 0 means wait indefinitely

step([$class: 'RunUftTestBuildStep']): Bumblebee Local UFT Test Runner

  • testPath : String
    Path to a test folder or test batch file (.mtb) which shall be executed
  • outputDirPath : String
    Path to the directory where to put JUnit-like execution results. Basedir of the fileset is the workspace root. If directory does not exist, it will be created

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.