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
apikey
file
attachFile
testrunname
labels
sprint
version
component
format
platform
comment
apikeyserver
jiraurlserver
proxyUrl
password
- Type:
class hudson.util.Secret
testrunnameserver
labelsserver
sprintserver
versionserver
componentserver
username
fileserver
attachFileServer
formatserver
platformserver
commentserver
testToRun
testrunkey
testassethierarchy
testCaseUpdateLevel
jirafields
testrunkeyserver
testassethierarchyserver
testCaseUpdateLevelServer
jirafieldsserver
disableaction
step([$class: 'TestReportDeployPublisher'])
: Publish results to QMetry for Jira version 3.X below
name
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.
file
Path of the result file/directory relative to build directory.
attachFile
Check for upload attachments in execution. Default value: false.
testrunname
Name of the test run to be created. For example: Test Run
labels
Comma separated names of Labels to be added to the test run. For example: label1, label2
sprint
Name of Sprint to be added to the test run. For example: Final sprint
version
Comma separated names of versions to be added to the test run. For example: version1, version2
component
Comma separated names of Components to be added to the test run. For example: component1, component2
format
platform
Name of Platform on which test run to be executed. For example: IOS
comment
Comment to be added to the test run.
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.
jiraurlserver
Your JIRA url. Example:https://qmetryjiraeval.qmetry.com/rest/qtm/latest/automation/importresults
proxyUrl
password
Password for your account.
- Type:
class hudson.util.Secret
testrunnameserver
Name of the test run to be created. For example: Test Run
labelsserver
Comma separated names of Labels to be added to the test run. For example: label1, label2
sprintserver
Name of Sprint to be added to the test run. For example: Final sprint
versionserver
Comma separated names of versions to be added to the test run. For example: version1, version2
componentserver
Comma separated names of Components to be added to the test run. For example: component1, component2
username
Username for your account.
fileserver
Path of the result file/directory relative to build directory
attachFileServer
Check for upload attachments in execution. Default value: false.
formatserver
platformserver
Name of Platform on which test run to be executed. For example: IOS
commentserver
Comment to be added to the test run.
testToRun
testrunkey
Provide Test Run key to append new results to existing Test Run.
testassethierarchy
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.
jirafields
Provide JSON array of custom jirafields.
testrunkeyserver
Provide Test Run key to append new results to existing Test Run.
testassethierarchyserver
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.
jirafieldsserver
Provide JSON array of custom jirafields.
disableaction
step([$class: 'TestReportDeployPublisherCloudV4'])
: Publish results to QMetry for Jira version 4.X above
testToRun
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.
file
Path of the result file/directory relative to build directory.
attachFile
Pass true to upload attachments in execution. Default value: false. For more details, Refer automation help documents.
format
disableaction
testCycleToReuse
Issue Key of the test cycle to be reused. If issue key of test cycle is not provided it will create new Cycle.
environment
Name of the environment on which test cycle has to be executed. Default Value is "No Environment".
build
Name of the build for test cycle execution
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
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
testCyclePriority
Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
testCycleStatus
Default value for Priority [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Cycle
testCycleSprintId
testCycleFixVersionId
testCycleSummary
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
testCycleStartDate
Pass date in 'dd/MMM/yyyy HH:mm' format
testCycleEndDate
Pass date in 'dd/MMM/yyyy HH:mm' format
testCycleReporter
Enter Valid User Account Id
testCycleAssignee
Enter Valid User Account Id
testCycleDescription
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
testCaseEstimatedTime
Pass time in 'HH:mm' format
testCaseReporter
Enter Valid User Account Id
testCaseAssignee
Enter Valid User Account Id
testCaseDescription
testCasePrecondition
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
testCasePriority
Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
testCaseStatus
Default value for Status [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Case
testCaseSprintId
testCaseFixVersionId
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
jiraUrlServer
Your JIRA url. Example:http://qtm4j.qmetry.com:8080/rest/qtm4j/automation/latest/importresult
proxyUrl
username
Username for your account.
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.
formatServer
fileServer
Path of the result file/directory relative to build directory.
testCycleToReuseServer
Issue Key of the test cycle to be reused. If issue key of test cycle is not provided it will create new Cycle.
environmentServer
Name of the environment on which test cycle has to be executed. Default Value is "No Environment".
buildServer
Name of the build for test cycle execution
attachFileServer
Pass true to upload attachments in execution. Default value: false. For more details, Refer automation help documents.
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
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
testCyclePriorityServer
Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
testCycleStatusServer
Default value for Priority [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Cycle
testCycleSprintIdServer
testCycleFixVersionIdServer
testCycleSummaryServer
testCycleStartDateServer
Pass date in 'dd/MMM/yyyy HH:mm' format
testCycleEndDateServer
Pass date in 'dd/MMM/yyyy HH:mm' format
testCycleAssigneeServer
Enter Valid User Account Id
testCycleReporterServer
Enter Valid User Account Id
testCycleDescriptionServer
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
testCaseEstimatedTimeServer
Pass time in 'HH:mm' format
testCaseAssigneeServer
Enter Valid User Account Id
testCaseReporterServer
Enter Valid User Account Id
testCaseDescriptionServer
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
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
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
testCasePriorityServer
Default value for Priority [High,Blocker,Low,Medium]. To get other values check under Qmetry > Configuration > Priority
testCaseStatusServer
Default value for Status [Done,In Progress,To Do]. To get other values check under Qmetry > Configuration > Statuses > Test Case
testCaseSprintIdServer
testCaseFixVersionIdServer
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.