| Table of Contents | ||
|---|---|---|
|
...
(A) Select QMetry > Integrations.
(B) As an alternate way, open QMetry > Test Recorder. Then click on the Configuration icon above the tree.
On Integration screen, select Cloud or Server versions that you want to integrate with QAS.
By default, Form is displayed to enter Integration details.
...
| Parameter | Type | Required | Description |
|---|---|---|---|
| Alias Name | string | Yes | QTM4J Integration Alias Name as per user preference. |
| URL | string | Yes | QTM4J URL to upload execution test results. Example: http://qtm4jmssql.qmetry.com:8080/rest/qtm/latest/automation/importresults |
apiKey | 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. |
| Username | string | Yes | Username to authenticate the login in QTM4J application. |
| Password | string | Yes | Password to to authenticate the login in QTM4J application. |
| format | string | Yes | Format of result file to be imported. Supported formats:
|
| testAssetHierarchy | string | No | Level of Hierarchy : Test Scenario-Test Case Or Test Case-Test Step
|
testCaseUpdateLevel | number | 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. |
testRunName | string | No | Name of the test run to be created. Default value: Test Run |
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. |
| isZip | boolean | No | Pass true for ZIP upload or pass false for single file upload. Default value: false Single test run will be created for multiple files within a zip. |
| testRunKey | string | No | Provide Test Run key to append new results to existing Test Run. |
| attachFile | boolean | No | Pass true for attachments upload in execution. Default value: false. |
| JIRAFields | JSON | No | Check specific Automation custom fields possible value and format here. |
...
Once you save the integration, it appears on the Integration List.
To edit the integration details, click on the Edit icon.
Modify the details and click Update to save the details.
Upload Test Results of already Executed Test Case
Else, click on the Save & Upload button to save the integration and upload the execution results into QTM4J.
...
Automation test suite/test cases will be created in QTM4J.
Push Test Results to QTM
...
Option 1. Open the Integration screen (QMetry > Integration with QMetry).
On the Integration list, click on the Upload button for the integration to which you want to upload the test results.
Option 2. Click on the Upload option and select QTM4J.
If the integration already exists, then the integration name will appear on the list. Select the one. In the absence of saved integration, click Other and follow Option 1.
The Upload 2.
To upload automated test cases with their execution results to QTM4J 4x, click Upload.
Select QTM4J 4x on the list.
Option 2. In the absence of saved integration, click on the Upload option and select Other.
The Integration screen opens. You can add a new Integration and Save it.
You can also upload the execution directly while saving the Integration by clicking on the Save & Upload button.
The saved Integrations are displayed on the Integration list.
Click on the Upload icon for the integration to which you want to upload the test results.
The Upload Results pop-up opens.
Select either of the following options:
...
| Note |
|---|
Note: If the QTM4J Configuration is set as default, then the results will be uploaded to QTM4J as and when a build is triggered through CI/CD tools. |
.png?version=1&modificationDate=1576149975539&cacheVersion=1&api=v2)
If the QTM4J configuration is set as default, then the qmetry.properties file, under the resources directory (resources/qmetry.properties), will auto populate the configuration details.
...