QMetry Test Management plugin for Jenkins is designed to seamlessly integrate your CI/CD pipeline with QMetry Test Management.
...
Parameter | Type | Required | Description | |||||
QMetry URL | string | Yes | QMetry Test Management 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. | |||||
| Proxy URL | string | No | Enter Proxy URL if you have configured any Proxy. | |||||
Automation Framework | string | Yes | Format of result file to be imported. Supported formats:
| |||||
| Automation Hierarchy | string | No | Hierarchy which will be used to parse test result files on QTM. Supported formats are :- JUnit 1 - Use current Hierarchy in which JUnit Testcase is treated as TestStep and Testsuite is treated as Testcase (default) 2 - Use Junit Testcase as Testcase and link all those (from all testsuites and all files of Junit) to one Testsuite 3 - Create Multiple Testsuites and then link their respective testcases in corresponding Testsuites TestNG 1 - Use class 'name' as Testcase and test-method as TestStep (default) 2 - Use test-method as Testcase 3 - Use test 'name' as Testcase and test-method as TestStep | |||||
| Result File(s) Path/Directory | string | Yes | Path wherein your result file to be uploaded. Supported file extensions: .json, .xml and .zip (zip file must contain files of the format given in the 'Automation Framework' param). | |||||
| Test Suite ID | string | No | Key of the test suite exists in QMetry. In the absence of Key, a new test suite will be created. Note: If for Junit - 3 - Create Multiple Testsuites and then link their respective testcases in corresponding Testsuites - is chosen, then the parameter Test Suite ID will be ignored. | |||||
| Test Suite Name | string | No | If existing "testsuiteId" is not being used and auto-generated name for the new test suite is not desired, then a custom test suite name can be entered for this parameter. Note: If for Junit - 3 - Create Multiple Testsuites and then link their respective testcases in corresponding Testsuites - is chosen, then this parameter will be ignored. | |||||
| Project | string | Yes | ID/Key/Name of the Project within which the test suite will be created. | |||||
| Release | string | *No | ID/Name of the Release in which the test execution will be created. If Release is not mentioned, then Default Release will be considered. | |||||
| Cycle | string | No | ID/Name of the Cycle in which the test execution will be created. If Cycle is not mentioned, then Default Cycle will be considered. | |||||
| Build | string | No | Build Name/Id. In the absence of a value, it will create the default build. | |||||
| Platform | string | No | Name of Platform on which test run to be executed. | |||||
| Test Case Fields | JSON | No | Mention system defined fields and user defined fields for test case as shown in Test Case JSON format below. All the mandatory fields other than Summary should be mentioned in this parameter. | |||||
| Test Suite Fields | JSON | No | Mention system defined fields and user defined fields for test case as shown in Test Suite JSON format below. All the mandatory fields other than Summary should be mentioned in this parameter. This parameter will be ignored if existing Test suite Id is used to upload results. |
...
4. Finally check test execution page in QMetry and review your test run results.
Pipeline
QMetry Test Management supports Jenkins Pipeline for implementing and integrating continuous delivery pipelines into Jenkins.
Let’s create a standard Pipeline job in Jenkins.
...
The Add Parameter drop-down is enabled with the list of parameter types. Use the drop-down button to add as many parameters as you need.
There are different parameter types available. The way parameters take effect according their respective parameter type.
For example,
Choice Parameter and String Parameter are selected, and corresponding parameters are added as shown below.
...
| Expand | ||
|---|---|---|
| ||
Version 1.8 Release Date: 2019/09/25 Summary: Improvements Details:
|
...
| Expand | ||
|---|---|---|
| ||
Version 1.7 Release Date: 2019/05/28 Summary: Improvements Details:
|
...