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.

QMetry for JIRA - Test Management Plugin

step([$class: 'QTM4JResultPublisher']): Publish test result to QMetry for JIRA Old

  • name
    • Type: String
  • apikey
    • Type: String
  • file
    • Type: String
  • attachFile
    • Type: boolean
  • testrunname
    • Type: String
  • labels
    • Type: String
  • sprint
    • Type: String
  • version
    • Type: String
  • component
    • Type: String
  • format
    • Type: String
  • platform
    • Type: String
  • comment
    • Type: String
  • apikeyserver
    • Type: String
  • jiraurlserver
    • Type: String
  • proxyUrl
    • Type: String
  • password
    • Type: class hudson.util.Secret
  • testrunnameserver
    • Type: String
  • labelsserver
    • Type: String
  • sprintserver
    • Type: String
  • versionserver
    • Type: String
  • componentserver
    • Type: String
  • username
    • Type: String
  • fileserver
    • Type: String
  • attachFileServer
    • Type: boolean
  • formatserver
    • Type: String
  • platformserver
    • Type: String
  • commentserver
    • Type: String
  • testToRun
    • Type: String
  • testrunkey
    • Type: String
  • testassethierarchy
    • Type: String
  • testCaseUpdateLevel
    • Type: String
  • jirafields
    • Type: String
  • testrunkeyserver
    • Type: String
  • testassethierarchyserver
    • Type: String
  • testCaseUpdateLevelServer
    • Type: String
  • jirafieldsserver
    • Type: String
  • disableaction
    • Type: boolean
  • serverAuthenticationType
    • Type: String
  • personalAccessToken
    • Type: String

step([$class: 'TestReportDeployPublisher']): Publish results to QMetry for Jira version 3.X below

  • name
    • Type: String
  • apikey
    API Key is unique for a specific user in a single project . The result will be imported for the project associated with the given API Key.
    • Type: String
  • file
    Path of the result file/directory relative to build directory.
    • Type: String
  • attachFile
    Check for upload attachments in execution. Default value: false.
    • Type: boolean
  • testrunname
    Name of the test run to be created. For example: Test Run
    • Type: String
  • labels
    Comma separated names of Labels to be added to the test run. For example: label1, label2
    • Type: String
  • sprint
    Name of Sprint to be added to the test run. For example: Final sprint
    • Type: String
  • version
    Comma separated names of versions to be added to the test run. For example: version1, version2
    • Type: String
  • component
    Comma separated names of Components to be added to the test run. For example: component1, component2
    • Type: String
  • format
    • Type: String
  • platform
    Name of Platform on which test run to be executed. For example: IOS
    • Type: String
  • comment
    Comment to be added to the test run.
    • Type: String
  • apikeyserver
    API Key is unique for a specific user in a single project . The result will be imported for the project associated with the given API Key.
    • Type: String
  • jiraurlserver
    Your JIRA url. Example:https://qmetryjiraeval.qmetry.com/rest/qtm/latest/automation/importresults
    • Type: String
  • proxyUrl
    • Type: String
  • password
    Password for your account.
    • Type: class hudson.util.Secret
  • testrunnameserver
    Name of the test run to be created. For example: Test Run
    • Type: String
  • labelsserver
    Comma separated names of Labels to be added to the test run. For example: label1, label2
    • Type: String
  • sprintserver
    Name of Sprint to be added to the test run. For example: Final sprint
    • Type: String
  • versionserver
    Comma separated names of versions to be added to the test run. For example: version1, version2
    • Type: String
  • componentserver
    Comma separated names of Components to be added to the test run. For example: component1, component2
    • Type: String
  • username
    Username for your account.
    • Type: String
  • fileserver
    Path of the result file/directory relative to build directory
    • Type: String
  • attachFileServer
    Check for upload attachments in execution. Default value: false.
    • Type: boolean
  • formatserver
    • Type: String
  • platformserver
    Name of Platform on which test run to be executed. For example: IOS
    • Type: String
  • commentserver
    Comment to be added to the test run.
    • Type: String
  • testToRun
    • Type: String
  • testrunkey
    Provide Test Run key to append new results to existing Test Run.
    • Type: String
  • testassethierarchy
    • Type: String
  • testCaseUpdateLevel
    Test Case update level while reusing test case, starts from 0 to 2. (This is only applicable when you use TestCase-TestStep Hierarchy option) Default :- No change in test steps while reusing Test Case.
    • Type: String
  • jirafields
    Provide JSON array of custom jirafields.
    • Type: String
  • testrunkeyserver
    Provide Test Run key to append new results to existing Test Run.
    • Type: String
  • testassethierarchyserver
    • Type: String
  • testCaseUpdateLevelServer
    Test Case update level while reusing test case, starts from 0 to 2. (This is only applicable when you use TestCase-TestStep Hierarchy option) Default :- No change in test steps while reusing Test Case.
    • Type: String
  • jirafieldsserver
    Provide JSON array of custom jirafields.
    • Type: String
  • disableaction
    • Type: boolean
  • serverAuthenticationType
    • Type: String
  • personalAccessToken
    Enter Personal Access Token of your account.
    • Type: String

step([$class: 'TestReportDeployPublisherCloudV4']): Publish results to QMetry for Jira version 4.X above

  • testToRun
    • Type: String
  • apikey
    API Key is unique for a specific user in a single project . The result will be imported for the project associated with the given API Key.
    • Type: String
  • file
    Path of the result file/directory relative to build directory.
    • Type: String
  • attachFile
    Pass true to upload attachments in execution. Default value: false. For more details, Refer automation help documents.
    • Type: boolean
  • format
    • Type: String
  • disableaction
    • Type: boolean
  • testCycleToReuse
    Issue Key of the test cycle to be reused. If issue key of test cycle is not provided it will create new Cycle.
    • Type: String
  • environment
    Name of the environment on which test cycle has to be executed. Default Value is "No Environment".
    • Type: String
  • build
    Name of the build for test cycle execution
    • Type: String
  • testCycleLabels
    Comma separated names of Labels to be added to the test cycle. For example: label1, label2 To get values check under: Qmetry > Configuration > Labels
    • Type: String
  • testCycleComponents
    Comma separated names of Components to be added to the test cycle. For example: component1, component2 To get values check under: Qmetry > Configuration > Component
    • Type: String
  • testCyclePriority
    Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
    • Type: String
  • testCycleStatus
    Default value for Priority [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Cycle
    • Type: String
  • testCycleSprintId
    • Type: String
  • testCycleFixVersionId
    • Type: String
  • testCycleSummary
    • Type: String
  • testCycleCustomFields
    Enter Test Cycle Custom Fields in Json Array Format.
    For example: [{"name": "custom field 1", "value": "high,medium,low"}, {"name": "custom field 2", "value": "29/May/2020"}]
    To get more information check under: Qmetry > Configuration > Custom Fields > Test Cycle
    • Type: String
  • testCycleStartDate
    Pass date in 'dd/MMM/yyyy HH:mm' format
    • Type: String
  • testCycleEndDate
    Pass date in 'dd/MMM/yyyy HH:mm' format
    • Type: String
  • testCycleReporter
    Enter Valid User Account Id
    • Type: String
  • testCycleAssignee
    Enter Valid User Account Id
    • Type: String
  • testCycleDescription
    • Type: String
  • testCaseLabels
    Comma separated names of Labels to be added to the test case. For example: label1, label2 To get values check under: Qmetry > Configuration > Labels
    • Type: String
  • testCaseEstimatedTime
    Pass time in 'HH:mm' format
    • Type: String
  • testCaseReporter
    Enter Valid User Account Id
    • Type: String
  • testCaseAssignee
    Enter Valid User Account Id
    • Type: String
  • testCaseDescription
    • Type: String
  • testCasePrecondition
    • Type: String
  • testCaseComponents
    Comma separated names of Components to be added to the test case. For example: component1, component2 To get values check under: Qmetry > Configuration > Component
    • Type: String
  • testCasePriority
    Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
    • Type: String
  • testCaseStatus
    Default value for Status [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Case
    • Type: String
  • testCaseSprintId
    • Type: String
  • testCaseFixVersionId
    • Type: String
  • testCaseCustomFields
    Enter Test Case Custom Fields in Json Array Format.
    For example: [{"name": "custom field 1", "value": "high,medium,low"}, {"name": "custom field 2", "value": "29/May/2020"}]
    To get more information check under: Qmetry > Configuration > Custom Fields > Test Case
    • Type: String
  • jiraUrlServer
    Your JIRA url. Example:http://qtm4j.qmetry.com:8080/rest/qtm4j/automation/latest/importresult
    • Type: String
  • proxyUrl
    • Type: String
  • username
    Username for your account.
    • Type: String
  • password
    Password for your account.
    • Type: class hudson.util.Secret
  • apikeyServer
    API Key is unique for a specific user in a single project . The result will be imported for the project associated with the given API Key.
    • Type: String
  • formatServer
    • Type: String
  • fileServer
    Path of the result file/directory relative to build directory.
    • Type: String
  • testCycleToReuseServer
    Issue Key of the test cycle to be reused. If issue key of test cycle is not provided it will create new Cycle.
    • Type: String
  • environmentServer
    Name of the environment on which test cycle has to be executed. Default Value is "No Environment".
    • Type: String
  • buildServer
    Name of the build for test cycle execution
    • Type: String
  • attachFileServer
    Pass true to upload attachments in execution. Default value: false. For more details, Refer automation help documents.
    • Type: boolean
  • testCycleLabelsServer
    Comma separated names of Labels to be added to the test cycle. For example: label1, label2 To get values check under: Qmetry > Configuration > Labels
    • Type: String
  • testCycleComponentsServer
    Comma separated names of Components to be added to the test cycle. For example: component1, component2 To get values check under: Qmetry > Configuration > Component
    • Type: String
  • testCyclePriorityServer
    Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
    • Type: String
  • testCycleStatusServer
    Default value for Priority [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Cycle
    • Type: String
  • testCycleSprintIdServer
    • Type: String
  • testCycleFixVersionIdServer
    • Type: String
  • testCycleSummaryServer
    • Type: String
  • testCycleStartDateServer
    Pass date in 'dd/MMM/yyyy HH:mm' format
    • Type: String
  • testCycleEndDateServer
    Pass date in 'dd/MMM/yyyy HH:mm' format
    • Type: String
  • testCycleAssigneeServer
    Enter Valid User Account Id
    • Type: String
  • testCycleReporterServer
    Enter Valid User Account Id
    • Type: String
  • testCycleDescriptionServer
    • Type: String
  • testCycleCustomFieldsServer
    Enter Test Cycle Custom Fields in Json Array Format.
    For example: [{"name": "custom field 1", "value": "high,medium,low"}, {"name": "custom field 2", "value": "29/May/2020"}]
    To get more information check under: Qmetry > Configuration > Custom Fields > Test Cycle
    • Type: String
  • testCaseEstimatedTimeServer
    Pass time in 'HH:mm' format
    • Type: String
  • testCaseAssigneeServer
    Enter Valid User Account Id
    • Type: String
  • testCaseReporterServer
    Enter Valid User Account Id
    • Type: String
  • testCaseDescriptionServer
    • Type: String
  • testCaseCustomFieldsServer
    Enter Test Case Custom Fields in Json Array Format.
    For example: [{"name": "custom field 1", "value": "high,medium,low"}, {"name": "custom field 2", "value": "29/May/2020"}]
    To get more information check under: Qmetry > Configuration > Custom Fields > Test Case
    • Type: String
  • testCaseLabelsServer
    Comma separated names of Labels to be added to the test case. For example: label1, label2 To get values check under: Qmetry > Configuration > Labels
    • Type: String
  • testCaseComponentsServer
    Comma separated names of Components to be added to the test case. For example: component1, component2 To get values check under: Qmetry > Configuration > Component
    • Type: String
  • testCasePriorityServer
    Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
    • Type: String
  • testCaseStatusServer
    Default value for Status [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Case
    • Type: String
  • testCaseSprintIdServer
    • Type: String
  • testCaseFixVersionIdServer
    • Type: String
  • serverAuthenticationType
    • Type: String
  • personalAccessToken
    Enter Personal Access Token of your account.
    • Type: String

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.