Release Notes

Release Notes

Starting December 5, 2025, QMetry for Bamboo – DevOps/CD documentation moved from its location on Atlassian to a dedicated, standalone page. For the latest updates, refer to Release Notes (QTM4J Bamboo Integration-DevOps/CD).

QTM4J Bamboo Integration – DevOps / CD v1.1.11

Release Date: 2024-08-14

Version 1.1.11

Summary: Improvement

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.1.10

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.1.9

Summary: Improvement

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.1.8

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-18

Version 1.1.5

Summary: Improvement

Details: 

  • Added support of the Pre-condition field for test cases.

Release Date: 2023-03-29

Version 1.1.4

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-02-10

Version 1.1.3

Summary: Improvement

Details: 

  • Compatible with QTM4J Server/Datacenter v4.3.0 and Bamboo Sever v9.2.1

    • 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-01

Version 1.1.2

Summary: Improvement

Details: 

  • QTM4J Bamboo Integration - DevOps / CD v1.1.2 now supports Jira authentication for server hosting using PAT (Personal Access Token).

Release Date: 2021-04-17

Version 1.1.1

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: 2020-12-11

Version 1.1

Summary: Improvement

Details:

  • Provided support to custom fields for Jira Cloud.

  • Bamboo Remote node support.

Release Date: 2020-04-25

Version 1.0.9

Summary: Improvement

Details:

  • Compatibility with QMetry Test Management for Jira - Server/Data Center v4.0

  • Compatibility with Bamboo v7.1.1

Release Date: 2019-07-06

Version 1.0.8

Summary: Improvement

Details:

  • Compatibility with QMetry for Jira v4.0

  • Compatibility with Bamboo v7.0

Release Date: 2019-01-25

Version 1.0.7

Summary: Improvements

Details:

  • Compatibility with QMetry for Jira latest version

Release Date: 2018-09-18

Version 1.0.6

Summary: Improvements

Details:

  • Included support for Specflow Framework

  • Compatibility with Bamboo v6.6.2

  • Added ability to update, replace or keep steps while reusing test cases

  • Ability to upload attachment

Release Date: 2018-02-23

Version 1.0.5

Summary: Support for Bamboo latest version

Details:

  • Included support for HP UFT Framework

  • Compatibility with Bamboo v6.4

Release Date: 2018-02-05

Version 1.0.3

Summary: Compatibility with QMetry for Jira Cloud and Support for Jira Custom Fields.

Details:

1. Included support for all Jira Fields i.e Custom and System Fields.

2. Easy way to track your build - Build number would be appended on the Test Run Summary field.

3. Ability to reuse and existing Test Run issue, automation results would be appended to the existing issue id.

4. Create hierarchy of TestCase-TestSteps or TestScenario-TestCases by setting Test Asset Hierarchy.