Release Notes
- Mrunalini Potnis
- Punit Samtani
QMetry for Jira - Test Management Plugin v1.25
Release Date: 2024-08-14
Version 1.25
Summary: Improvements
Details:
- Introduced parameters "automationHierarchy" and "appendTestName" for Cloud version.
- The 'automationHierarchy' parameter provides flexibility to decide the Test Cycle- Test Case - Test Step hierarchy created for the automation result upload of TestNG and JUnit frameworks. The automation hierarchy can take values 1, 2, and 3, each with specific behavior tailored for different frameworks; more details are available on the Automation API page.
- The 'appendTestName' parameter enables easier identification of automation test cases once uploaded to QTM4J. This parameter applies only for TestNG and JUnit framework uploads with automation hierarchy as 2 and 3.
- Teams utilizing the TestNG can choose to auto-append the Test Name before the TestMethod Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify the test method belongs to which test while reviewing the TestNG results in QTM4J.
- Teams using the JUnit can choose to auto-append the Test Suite Name before the TestCase Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify the automated test case belonging to which test suite while reviewing the JUnit results in QTM4J.
Previous Versions
Release Date: 2024-05-30
Version 1.24
Summary: Data Residency Support in Australia
Details:
Compatible with QTM4J Cloud v4.11.1: QTM4J Cloud v4.11.1 now supports data residency in Australia for new cloud installations only.
Release Date: 2024-04-11
Version 1.23
Summary: Improvements
Details:
- Introduced parameters "automationHierarchy" and "appendTestName".
- The 'automationHierarchy' parameter provides flexibility to decide the Test Cycle- Test Case - Test Step hierarchy created for the automation result upload of TestNG and JUnit frameworks. The automation hierarchy can take values 1, 2, and 3, each with specific behavior tailored for different frameworks; more details are available on the Automation API page.
- The 'appendTestName' parameter enables easier identification of automation test cases once uploaded to QTM4J. This parameter applies only for TestNG and JUnit framework uploads with automation hierarchy as 2 and 3.
- Teams utilizing the TestNG can choose to auto-append the Test Name before the TestMethod Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify the test method belongs to which test while reviewing the TestNG results in QTM4J.
- Teams using the JUnit can choose to auto-append the Test Suite Name before the TestCase Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify the automated test case belonging to which test suite while reviewing the JUnit results in QTM4J.
Release Date: 2024-01-12
Version 1.22
Summary: Improvement
Details:
- Introduced parameter "matchTestSteps" that allows reusing an existing test case version without matching its test steps and importing only the test case execution status from the automation result uploads of JUnit, TestNG, and Cucumber frameworks.
Release Date: 2023-07-24
Version 1.21
Summary: Improvement
Details:
- Added support of the Pre-condition field for test cases.
Release Date: 2023-03-28
Version 1.20
Summary: Improvement
Details:
- Compatible with QTM4J Cloud v4.7.0 - Organize automated test cases and test cycles into a folder by setting the folder id when uploading automation results.
Release Date: 2023-01-31
Version 1.19
Summary: Improvement
Details:
- Compatible with QTM4J Server/Datacenter v4.3.0.
- Organize automated test cases and test cycles into a folder by setting the folder path when uploading automation results.
- Set test case execution fields like comments, actual time, assignee, and other custom field values while uploading the automation results.
Release Date: 2022-06-02
Version 1.18
Summary: Improvement
Details:
- QMetry for Jira - Test Management plugin v1.18 for Jenkins now supports Jira authentication for server hosting using PAT (Personal Access Token).
Release Date: 2021-04-17
Version 1.17
Summary: Improvement
Details:
- Compatibility with QMetry for Jira - Test Management latest version.
- Included support for all Jira Fields i.e. Custom and System Fields.
Release Date: 2021-03-16
Version 1.16
Summary: Improvement
Details:
Provided support to custom fields for Jira Cloud.
Release Date: 2020-04-25
Version 1.15
Summary: Improvement
Details:
- Compatibility with QMetry Test Management for Jira - Server/Data Center v4.0
Release Date: 2020-02-12
Version 1.14
Summary: Bug Fix
Details:
- Fixed a bug that allowed transmission of password in plain text as part of the configuration form.
Release Date: 2019-07-09
Version 1.13
Summary: Improvement
Details:
- Compatibility with QMetry for Jira v4.0
Release Date: 2019-02-26
Version 1.12
Summary: Improvement
Details:
- Enhanced support for Jenkins Slave.
Version 1.11
Release Date: 2018-09-26
Summary: Improvements in automation import via Jenkins
Details:
- Trigger build through Pipeline Project.
- Parse QMetry parameters as inputs to provide values dynamically at run-time.
- Support for Specflow Framework.
- Choose to ‘Append’, ‘Override’ or make ‘No changes’ in test steps when reusing test cases.
- Upload attachment for Cucumber and QAS frameworks.
Version 1.10
Summary: Improvement
Details:
- The new builds now support integration with the Master/Agent distributed builds environment. This means if the automation result file is generated on an Agent, plugin will pick the files from Agent and push results to QMetry.
Version 1.9
Summary: Improvement
Details:
- Added support for HP UFT
Version 1.8
Summary: Improvements
Details:
- Included support for all Jira Fields i.e Custom and System Fields.
- Easy way to track your build - Build number would be appended on the Test Run Summary field.
- Ability to reuse and existing Test Run issue, automation results would be appended to the existing issue id.
- Create hierarchy of TestCase-TestSteps or TestScenario-TestCases by setting Test Asset Hierarchy.