Page Comparison

Table of Contents

...

10. Configure the QTM4J Bamboo Integration task. Now QTM4J Cloud also supported along with QTM4J Server.

Jira Cloud

Image RemovedImage Added

Parameter	Required	Description
Automation Api Key	Yes	Your API Key. 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.
Test Run Name	No	Name of the test run to be created. It will be appended with the Jenkins build Number.
Test Run Key	No	Existing Issue Key of Test Run. Test run will be appended with the test case and executions.
Result File path/Result Directory	Yes	Path to your result file to be uploaded. Example : The Bamboo plugin is expecting the file in BambooHome/xml-data/build-dir/<Project Name> If your project name is TestNGProject, then you will find a folder name with TestNGProject "Key Name" in bamboo home BambooHome/xml-data/build-dir/<Project Name> Your result file should be under BambooHome/xml-data/build-dir/<Project Name> The path that should be set in plugin configuration is "/Testng-result.xml"
Format	Yes	Format of result file to be imported. Supported formats: cucumber/json testng/xml junit/xml qas/json hpuft/xml specflow/json
Test Asset Hierarchy	Yes	Level of Hierarchy : Test Scenario-Test Case Or Test Case-Test Step
testCaseUpdateLevel	No	Test Case update level while reusing test case, starts from 0 to 2. (This is only applicable when you use TestCase-TestStep Hierarchy option) 0 Append test steps while reusing Test Case. 1 Override test steps while reusing Test Case. 2 No change in test steps while reusing Test Case. Default :- No change in test steps while reusing Test Case.
attachFile	No	Check for upload attachments in execution. Default value: false.
Platform	No	Name of Platform on which test run to be executed.
Labels	No	Comma separated names of Labels to be added to the test run.
Versions	No	Comma separated names of versions to be added to the test run.
Components	No	Comma separated names of Components to be added to the test run.
Sprint	No	Name of Sprint to be added to the test run.
Comment	No	Comment to be added to the test run.
JIRAFields	No	Check specific Automation custom fields possible value and format here.

Jira Server

Image RemovedImage Added

Parameter	Type	Required	Description
Jira URL	String	Yes	Enter JIRA URL
Basic Authentication OR Personal Access Token	String	Yes	Basic Authentication Basic authentication with Jira's credentials. Jira Username Jira Password: Password for Jira instance.
Basic Authentication OR Personal Access Token	String	Yes	Personal Access Token If the Allow basic authentication on API calls option is disabled in Jira, then Personal Access Token is required for authentication. To generate personal access token, perform the following steps: Go to User Profile of your Jira. Click on Personal Access Tokens and click on Create token.
Automation Api Key	string	Yes	Your API Key. 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.
Format	selection	Yes	Format of result file to be imported. Supported formats: cucumber/json testng/xml junit/xml qas/json hpuft/xml specflow/json
Result File path/Result Directory	string	Yes	Path to your result file to be uploaded. Example : The Bamboo plugin is expecting the file in BambooHome/xml-data/build-dir/<Project Name> If your project name is TestNGProject, then you will find a folder name with TestNGProject "Key Name" in bamboo home BambooHome/xml-data/build-dir/<Project Name> Your result file should be under BambooHome/xml-data/build-dir/<Project Name> The path that should be set in plugin configuration is "/Testng-result.xml"
Test Run Name	string	No	Name of the test run to be created. It will be appended with the Jenkins build Number.
Test Run Key	string	No	Existing Issue Key of Test Run. Test run will be appended with the test case and executions.
Test Asset Hierarchy	selection		Level of Hierarchy : Test Scenario-Test Case Or Test Case-Test Step
testCaseUpdateLevel		No	Test Case update level while reusing test case, starts from 0 to 2. (This is only applicable when you use TestCase-TestStep Hierarchy option) 0 Append test steps while reusing Test Case. 1 Override test steps while reusing Test Case. 2 No change in test steps while reusing Test Case. Default :- No change in test steps while reusing Test Case.
attachFile	selection	No	Check for upload attachments in execution. Default value: false.
Platform	string	No	Name of Platform on which test run to be executed.
Labels	string	No	Comma separated names of Labels to be added to the test run.
Versions	string	No	Comma separated names of versions to be added to the test run.
Components	string	No	Comma separated names of Components to be added to the test run.
Sprint	string	No	Name of Sprint to be added to the test run.
Comment	string	No	Comment to be added to the test run.
JIRAFields	`JSON`	No	Check specific Automation custom fields possible value and format here.

...

Versions Compared

Old Version 8

New Version Current

Key