Release Notes (QTM4J Bamboo Integration-DevOps/CD)
QTM4J Bamboo Integration-DevOps/CD Release Notes
QTM4J Bamboo Integration – DevOps/CD v1.1.11
August 14, 2024
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
Previous Versions
QTM4J Bamboo Integration – DevOps/CD v1.1.10
May 30, 2024
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.
QTM4J Bamboo Integration – DevOps/CD v1.1.9
April 11, 2024
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.
QTM4J Bamboo Integration – DevOps/CD v1.1.8
January 12, 2024
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.
QTM4J Bamboo Integration – DevOps/CD v1.1.5
July 18, 2023
Summary: Improvement
Details:
Added support for the Precondition field for test cases.
QTM4J Bamboo Integration – DevOps/CD v1.1.4
March 29, 2023
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.
QTM4J Bamboo Integration – DevOps/CD v1.1.3
February 10, 2023
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.
QTM4J Bamboo Integration – DevOps/CD v1.1.2
June 1, 2022
Summary: Improvement
Details:
QTM4J Bamboo Integration - DevOps/CD v1.1.2 now supports Jira authentication for server hosting using PAT (Personal Access Token).
QTM4J Bamboo Integration – DevOps/CD v1.1.1
April 17, 2021
Summary: Improvement
Details:
Compatibility with QMetry for Jira - Test Management latest version.
Included support for all Jira Fields, like Custom and System Fields.
QTM4J Bamboo Integration – DevOps/CD v1.1
December 11, 2020
Summary: Improvement
Details:
Provided support to custom fields for Jira Cloud.
Bamboo Remote node support.
QTM4J Bamboo Integration – DevOps/CD v1.0.9
April 25, 2020
Summary: Improvement
Details:
Compatibility with QMetry Test Management for Jira - Server/Data Center v4.0
Compatibility with Bamboo v7.1.1
QTM4J Bamboo Integration – DevOps/CD v1.0.8
July 6, 2019
Summary: Improvement
Details:
Compatibility with QMetry for Jira v4.0
Compatibility with Bamboo v7.0
QTM4J Bamboo Integration – DevOps/CD v1.0.7
January 25, 2019
Summary: Improvements
Details:
Compatibility with QMetry for Jira latest version
QTM4J Bamboo Integration – DevOps/CD v1.0.6
September 18, 2018
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
QTM4J Bamboo Integration – DevOps/CD v1.0.5
February 23, 2018
Summary: Support for Bamboo latest version
Details:
Included support for HP UFT Framework
Compatibility with Bamboo v6.4
QTM4J Bamboo Integration – DevOps/CD v1.0.3
February 5, 2018
Summary: Compatibility with QMetry for Jira Cloud and Support for Jira Custom Fields.
Details:
1. Included support for all Jira Fields, like Custom and System Fields.
2. Easy way to track your build - The Build number would be appended to 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 a hierarchy of TestCase-TestSteps or TestScenario-TestCases by setting Test Asset Hierarchy.