| Table of Contents |
|---|
...
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> |
| 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. |
| 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. |
...
Parameter | Type | Required | Description |
QMetry Automation API URL | String | Yes | Enter JIRA URL |
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. |
Jira Username | string | Yes | JIRA Username |
Jira Password | string | Yes | Password for JIRA instance. |
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> |
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. | |
| 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. |
...
3. Configure MS Build Executable
Click on Add New Executablenew executable.
Set path for executable.
...
4. MS Build Configuration
Project File: Give path to the Solution. Project File or MSBuild project will be executed when this Job runs.
5. VS Test Executable
Click on Add new executable.
Add executable for vstest.
...