/
Release Notes

Back to QMetry All Products Help Page

Release Notes

Owned by Mrunalini Potnis
Last updated: Jan 04, 2025 by Niharika Choudhury
102 min read

Build 8.19.0 - Release Date: 2025-01-04

Summary: Improvements & Bug Fixes

 

Permission Enhancements

  • 'Release and Cycle' permissions have been introduced to control the creation, modification, archiving, and deletion of releases and cycles within a project. These permissions are now separate from the 'Modify' project permissions, offering more granular control over their management.

  • Users with 'Modify' permissions for test cases, requirements, or test suites can now archive their respective folders. Archiving folder permissions are now separated from 'Delete' and merged with 'Modify'.

  • Users with 'Execute' or 'Modify' permissions for Test Suites can now update the 'Execution Assignee' and 'Planned Date' for test case runs.

Execution Screen Enhancements

  • The test execution screen now displays the execution status for each group combination of a parameterized test case run, helping users quickly identify any combinations that have failed or remained unexecuted. This feature is available only for projects that have enabled the setting to derive the test case execution status from the statuses of its steps.

  • The Test Execution screen now shows the folder path for test cases, making it easier for users to identify them within a specific folder hierarchy. Users can sort the folder path, filter test cases, and view those belonging to a selected folder or its entire hierarchy. Additionally, the folder path column is now visible in the test case list view when linking test cases to the test suite.

Report Enhancements 

  • A new 'Total API Utilization Report' has been introduced under the 'Login Summary Dashboard,' enabling administrators to track the daily and hourly allocation and consumption of Open API and Automation API requests.

  • Super Admins can now monitor API usage by setting up email alerts for daily or hourly Open API and Automation API requests when they near a defined threshold limit, helping to prevent overages.

Security Enhancements

  • Users now have the option to mask sensitive information, such as API keys and authorization tokens, in header values or the webhook body when creating or editing a CI/CD rule. These masked values will remain hidden in the user interface and cannot be retrieved, providing an added layer of protection for sensitive data.

  • The browser right-click options for image thumbnails and previews are now restricted to avoid unintentionally sharing URLs with unauthorized individuals.

Miscellaneous Enhancements 

  • Navigating to the Projects menu now displays and highlights the currently logged-in project at the top of the list, making it more convenient for project administrators to access and manage settings.

  • The 'Projects' section in the QMetry menu is now called 'Project Management'. This change clarifies that all project setup tasks are managed within this section, making it easier for users to locate and carry out these actions. The former 'Project/Release/Cycle' menu has been renamed 'Projects'. A new sub-menu titled 'Releases & Cycles' has been added under 'Project Management' to give users easier access to the Release and Cycle management screens.

Jira Integration Add-on Upgrade 

  • Release v8.19 requires installation/upgrade of the QMetry-Jira Integration app to v2.3.1 for organizations using Jira 10 and v2.3.1_jira9 for organizations using Jira 9 or below. For customers utilizing Jira Cloud, the add-on will upgrade automatically.

Bug Fixes

  • Fixed a bug that caused unarchived test cases to be displayed in the archived list when deleting test cases in bulk.

  • Fixed a bug that exported a blank data file using the 'export raw data' option from custom reports using inbuilt folder selection filters.

  • Fixed a bug that prevented the display of integrated Jira projects under the Project Integration section when syncing a QMetry project with multiple Jira projects.

  • Fixed a bug that prevented User Defined Fields (UDF) from appearing on the test execution screen's detail view for some cases.

 

Build 8.18.1 - Release Date: 2024-11-22

Summary: Bug Fixes

  • Fixed a bug where words in test case steps were split across lines in edit mode, impacting readability and editing.

  • Fixed a bug where selecting text in a test step caused it to become unselected and the text box to close abruptly in edit mode, disrupting the editing process and making text selection and modification difficult.

  • Fixed a bug that restricted the creation of users with email addresses and usernames containing an apostrophe ('), which also prevented sharing test assets with such users.

  • Fixed a bug that prevented users with test suite view-only permissions from seeing the 'Execute' button in the Test Suite's 'Test Executions' tab, which is needed to view the executions.

  • Fixed a bug that prevented the Jira fields section from loading into requirements in the cloned project if Jira integration was removed from the source project.

  • Fixed a bug that prevented non-admin users from setting build on the execution screen for dependent test cases until the execution screen page was refreshed manually.

  • Fixed a bug that prevented deleting custom dashboards with more than one gadget for certain cloud instances.

 

Compatibility

  • QMetry Jira Integration App v2.3.0 is compatible with Jira version 10.3.0 and QTM v8.18.1.

 

Build 8.18.0 - Release Date: 2024-10-26

Summary: New Features, Improvements & Bug Fixes

New Features

New AI Feature - QI Query Assistant (Currently in Beta, Only for Cloud)

  • Introducing the QI Query Assistant - a powerful AI feature that allows users to generate custom SQL reports directly from QMetry Insight using QMetry Intelligence (QI). The Query Assistant simplifies the reporting process, enabling users to create, modify, or understand SQL queries without requiring extensive SQL knowledge. The Query Assistant supports the following three use cases:

    • Generate a New Query - The QI Query generator creates SQL queries based on user-defined reporting needs expressed in simple English, aligned with the QMetry reports schema available in QMetry Insight.

    • Updating an Existing Query - The QI Query generator can help users modify existing SQL queries by adding fields and filters or implementing new logic and operators. To do this, users provide the existing SQL and clear instructions for the desired modifications in English. The output will be an updated custom SQL query reflecting these changes.

    • Explaining Query - The Query Assistant empowers users to understand SQL queries by providing explanations of their logic, tables and structure. This guidance enables users to comprehend the purpose and functionality of the query, aiding in debugging and troubleshooting.

  • Key Benefits: The classic advanced query custom reports feature requires users to manually write SQL queries based on the database schema, necessitating extensive SQL knowledge and an understanding of database tables and columns. Such requirements often lead to a reliance on technical teams and professional services. In contrast, QI empowers users with basic SQL knowledge to generate SQL queries quickly, significantly reducing the time and effort required.

  • Activation Instructions: To enable this feature, the QMetry Super Administrator must activate it by navigating to General Settings > AI Configurations.

  • How it Works: Upon activating the feature, users will see a new "QI View" under the Advanced Query Reports menu in QMetry Insights, alongside the existing Classic View. The QI View provides instructions and best practices for generating queries. Users can switch between the Classic SQL generation view and the QI View as needed.

  • Usage Statistics: System administrators can monitor the usage of the SQL generator feature for all users. Statistics for creating and updating reports using SQL queries generated by QI are accessible in General Settings > AI Configurations. Individual users can also view similar statistics tailored to their activities.

  • Identify QI-Generated Reports: Reports created using SQL queries generated using QI will display the QI logo when added to dashboards. The 'Custom Gadget' list view includes a 'QI generated' column to identify reports generated with SQL queries from QI.

  • Best Practices: All features operate according to the QMetry reports schema available in QMetry Insights. As a best practice, users must clearly describe their reporting needs in detail, specifying exact field names and any conditions or operations such as grouping, filtering, or sorting. The Query generator currently does not support the user-defined fields and works only with system fields.

New AI Features for Auto Generate Test Cases using QI (Currently in Beta, Only for Cloud)

  • Testers can now improve existing test case descriptions, pre-conditions, or step content using QMetry Intelligence (QI). For test steps, QI supports only the step description and expected outcome for content enhancement. Testers can enhance and refine the content using the following options, depending on their specific needs:

    • Regenerate Text: QI will rewrite the content for improved clarity or structure.

    • Suggest Alternatives: QI will provide alternative phrasing or wording options to enhance the content.

    • Add More Details to Text: QI will expand the content by including additional information or context.

    • Summarize Text: QI will condense the content into a shorter, more concise form while retaining key details.

    • Ask QI: Additionally, testers can prompt QI with specific commands such as Enrich Vocabulary, Adjust Tone (e.g. make it more formal or professional), Simplify Text, Proofread Text (e.g. check and correct grammar, spelling, and punctuation errors), Refine the Text or Make it More Engaging.

    • Note: This feature only generates text-based content. It will not retain any input that includes inline images, tables, URLs, or rich text data.

  • Testers can now generate or update all test steps on an existing test case using QMetry Intelligence (QI) based on the Test Case Summary and Description. Additionally, users can input a requirement or user-provided description, along with the test case description, to QI to generate test steps. This option allows testers to create test steps aligned with the scope outlined in the test case summary and description.

  • Direct Feedback: Testers can now share their improvement feedback from the QI interface about the generated test cases to help the QMetry product teams enhance the feature.

New Features for QMetry Jira Integration

  • QMetry now enhances security and streamlines authentication by supporting OAuth 2.0 for Jira Cloud and Jira Data Center integrations. This feature allows users to securely authorize QMetry to access Jira data without entering their credentials or API tokens, ensuring a more secure and compliant connection between the two tools. QMetry Admins can enable this optional extra security layer from the Integrations menu > Oauth settings to enhance authentication security with Jira. After this setting is enabled, users must authenticate their Jira accounts once using an OAuth verification token to create or update issues.

  • Release v8.18 requires installation/upgrade of the QMetry-Jira Integration app to version 2.2.9. For customers utilizing Jira Cloud, the add-on will upgrade automatically.

 

Improvements to Shareable Test Cases

  • Move shareable test cases, individually or in bulk, between folders within the same project or across different projects, just like regular test cases.

  • Copy shareable test cases, individually or in bulk, within the same project or across different projects, similar to regular test cases.

  • Import or re-import test cases that include linked shareable test cases using an Excel or CSV file. The shareable test cases must already exist in the projects, and the import file should contain the shareable test case key and the associated version to map during the import process.

Improvements to the Dashboards and Reports

  • Global filters are introduced on System and Custom dashboards, enabling users to view and apply common (i.e. shared) filters for all gadgets from the top of the dashboard. Instead of configuring filters for each gadget individually on a dashboard, users can now set shared global filters that apply simultaneously to all gadgets. Users still have the option to set specific and unique filters at the individual gadget level. When the global filters differ from those set on the gadget, an indication will be displayed, making it easier for users to identify discrepancies in the applied filters.

  • The Planned vs. Actual Execution gadget on the Test Execution Summary dashboard isenhanced to help QA teams monitor the progress of actual executions against planned dates.This improvement enables teams to assess current execution rates and determine therequired rates to meet delivery timelines based on the planned execution schedule.

  • All gadgets on the Test Execution Summary dashboard can now be filtered using Test Suite Folders.

Improvements to the Custom Reports

  • Pre-defined, ready-made browse folder filters for the Test Case, Test Suite, and Requirements modules are now available for users to add when creating custom reports using the Visual Reports or Advanced Query Reports modules.

  • The automation error messages and error trace fields for test step executions are available in the "teststepexecution" table within the Advanced Query Report module, enabling users to create custom reports using these fields.

Improvements to the Test Execution Screen

  • A new field, 'Planned Date,' has been introduced on the execution screen to help testers plan and track their assigned test case executions on specific dates. With both 'Planned' and 'Executed' dates now available, testers can easily monitor and compare their scheduled and actual execution timelines.

  • New options have been introduced on the Test Execution screen to export Test Executions and Test Cases with selected fields. Testers can export Test Executions including or excluding steps or Test Cases linked to those Test Executions with or without steps, depending on the fields they choose.

  • Two new duration fields, 'Automated TC Execution' and 'Automated Step Execution,' have been introduced on the execution screen to track the time taken for automated test cases and step executions, respectively. The durations are extracted and parsed from the automation result file uploads.

    • The 'Test Case Execution Time (Mins)' and 'Total Execution Time (Mins)' columns for automation executions on the Test Execution screen have been deprecated and will no longer store any values in the future.

  • The 'Test Case Estimated Time (mins)' column has been added to the Test Execution screen, enabling testers to easily view the estimated time for executing a test case.

Improvements to the Test Case Module

  • The option to 'Copy Steps from an Existing Test Case' has been introduced when creating or editing test case steps to enable testers to conveniently copy selected test steps from one test case to another within the same project or across different projects.


Improvements to Automation Agent

  • The Automation Agent now supports setting up recurring schedules for multiple test suite executions on the same agent, whether for the same test suite or different ones. When scheduling an execution command for an agent, all upcoming schedules for the agent are displayed, making it easier for testers to identify overlapping tasks. For multiple execution schedules set for the same time on the same agent, the agent will execute them sequentially on a first-come, first-served basis. The agent list screen now displays the total count of tasks 'Scheduled' and 'In Progress' for each agent.

New Features to User Provisioning through SCIM 2.0

  • The QMetry Administrator now has the option to allow QMetry to intelligently allocate and manage user license types from the IAM system when handling user provisioning using SCIM on the instance. In a QMetry instance with both Read-Only and Regular Licenses available:

    • Users with a Read-Only role across all projects will be automatically assigned/converted to a Read-Only License.

    • Users with a Non-Read-Only role in any project will be automatically assigned/converted to a Regular License.

  • When switching a user's license type from read-only to regular or vice versa, it's now optional to unassign the user from all groups if the user holds a Read-Only role across all projects. This rule applies when the user's license type is managed in the IAM system using the custom attribute 'QMetry_User_LicenseType'.

 

Bug Fixes

  • Fixed a bug that added an extra comma at the end of the last column for CSV exports of Requirements, Test Cases, Test Suites, Issues, and System and Custom reports.

  • Fixed bug that incorrectly displayed the 'Created By' field for the Azure work item created from within QMetry, showing the name of the user who configured the QMetry Azure integration instead of the user who created it.

  • Fixed a bug that prevented requirements import from Excel due to partially matching values encountered for the lookup list type field.

  • Fixed a bug that prevented viewing and downloading PDF and Word files containing an apostrophe (') or dash (-) in the file name.

  • Fixed a bug that caused an unsupported Jira team picker field type to appear in the integration field mapping configuration, allowing it to sync as both a requirement and issue field.

  • Fixed a bug that prevented test cases from being displayed as QI-generated after their details were updated, resulting in incorrect QI-generated statistics.

  • Fixed a bug that restricted the creation of users with email addresses containing an apostrophe ('), which also prevented sharing test assets with such users.

  • Fixed a bug that prevented assigning project and role for a user, along with user license type update from read-only to regular in the same operation.

  • Fixed a bug that allowed updating the actual outcome and execution status of testcases/steps for a closed test execution when the test execution was closed and another user had the same test execution session open.

  • Fixed a bug that prevented the execution of an advance query report using the DATE_SUB() function due to a parsing error in the WHERE clause.

  • Fixed a bug that prevented testers with execute permissions from adding comments for a testcase run in the Execution Detail View.

  • Fixed a bug that was causing inline attachments to not display in the descriptions of Requirements and Issues synced from Jira.

  • Fixed a bug that displayed a truncated summary for the shareable test case having a long summary when included in another test case.

Previous Versions

 

 

Build 8.17.1.1 - Release Date: 2024-09-20

Summary: Bug Fixes

  • Fixed bug that removed auto-generated test cases created with QI from the QI statistics after updating the test case steps.

  • Fixed a bug that intermittently removed the updated step execution comment after saving it on the test execution screen.

 

Build 8.17.1 - Release Date: 2024-07-27

Summary: New Features, Improvements & Bug Fixes

 

Generate Test Cases using QMetry Intelligence (Currently in Beta):

Testers can now generate functional test cases using QMetry Intelligence (QI) directly from a requirement or user-provided description. QI will also enable testers to generate test case details and steps for an existing test case using the same inputs, with the option to update the existing test case or create a new version.

  • Key benefits: The auto-generation feature accelerates the test case authoring phase by swiftly creating test cases with steps aligned to specified requirements. This ability reduces the manual effort of testers, allowing them to focus more on test case execution and validation. As a result, the feature saves valuable time during the testing lifecycle and enables teams to deliver releases faster.

  • How it works: The QI model extracts relevant details from a requirement or user-provided description to generate modular functional test cases with adequate coverage, ensuring thorough validation of the acceptance criteria.

    • For QI to generate test cases with higher accuracy, the requirement description must provide sufficient information in a structured use case format. The description should also contain acceptance criteria that clearly define the expected behaviour of the feature; decomposed stories will yield better results. These details enable QI to analyze the context and accurately identify test scenarios.

    • Testers can accept, modify, or reject the generated test cases before approving them for creation into the project's test case library.

    • For projects integrated with external trackers like Jira, Rally, or Azure to sync their requirements with QMetry, project administrators can configure up to two issue fields as input descriptions for QI to generate test cases.

  • Activation instructions: To enable all users to auto-generate test cases using the QI feature, the QMetry Super Administrator must activate the feature from the General Settings.

  • Usage Statistics: The administrators and testers can also view statistics on how the auto-generated test case feature is helping save time and effort for both them and their project teams.

 

Report Enhancements

  • System and custom report charts now display the total record count, making it easier for users to analyze the data.

  • PDF and Word exports of test cases and test executions now comply with FDA guidelines for regulated industries by displaying 'N/A' for empty fields and sections.

 

Administrative Enhancements

  • QMetry Super Administrators can now disable the feature at instance level that lets users generate and share embedded URLs for report dashboards with unrestricted access, in line with organizational policies.

  • When cloning a project, a confirmation pop-up is provided to remind administrators that the project will be in read-only mode until cloning is complete, helping them avoid initiating cloning during peak times.

 

Miscellaneous Enhancements

  • The default order for the Extent of Testing list has been updated so that a higher RPN indicates more intensive testing requirements. Similarly, the Risk Likelihood and Risk Impact lists have also been adjusted to align with this change.

  • In projects with the test case dependency feature enabled and auto-propagate status settings configured, the execution status of a dependent test case will automatically be marked as 'blocked' if its predecessor test case fails.

  • The 'Copy Link' button has been relocated from the Share pop-up to the details screen, and positioned next to the asset key, for easier access.

  • When exporting executions to PDF and Word formats, execution dependencies between test cases will now appear in a separate section for clearer organization.

 

Bug Fixes

  • Fixed a bug that blocked bulk copying of test cases when the source project had risk-based testing enabled.

  • Fixed a bug that caused tabular gadgets to lose their size and fail to display data correctly when enlarged on the custom dashboard.

  • Fixed a bug that prevented the 'Create Issue' screen from displaying for Jira-integrated projects when the Jira field name had a trailing space.

  • Fixed a bug that prevented all test cases linked directly to a Jira defect from displaying within QMetry's Test Case section on the Jira issue page.

  • Fixed a bug that caused Open API calls with a trailing forward slash to fail, resulting in a 404 error response upon execution.

  • Fixed a bug that prevented filtering test cases, test suites, requirements, and linked issues count with 0.

  • Fixed a bug that prevented filtering a custom gadget simultaneously on multiple date-type fields when designing it using Visual Reports.

  • Fixed a vulnerability due to the Apache library "commons-text-1.9.jar" used in the automation container by upgrading it to v1.11.

  • Fixed a bug that prevented archived projects from appearing on the Edit Fields configuration screen.

  • Fixed a bug that caused the steps to export in the incorrect order in the Excel file exported from the test case module.

  • Fixed a bug that prevented setting the system "read only" role as a default for newly created LDAP/SAML users.

  • Fixed a bug that prevented versioning test cases containing shareable steps and simultaneously syncing them for execution.

 

Build 8.17.0.1 - Release Date: 2024-06-11

Summary: Bug Fixes

  • Fixed a bug that prevented cycles from appearing under the cycle filter for the filtered releases under custom gadgets.

  • Fixed a bug that prevented save and discard buttons from appearing for Actual Outcome and Comments fields on the execution screen for parameterized test cases.

  • Fixed a bug that incorrectly reset the value of the Associated Cycle field to "None" for issues updated through a bulk update.

 

Build 8.17.0 - Release Date: 2024-06-01

Summary: New Features, Improvements & Bug Fixes

New Features

 

Test Case Dependency

  • Test case dependency refers to the relationship where the outcome of one test case depends on the successful execution of another. Managing these dependencies is crucial for ensuring a logical and organized testing process, especially for complex test scenarios.

    • Testers can now define execution dependencies between test cases as Predecessor orSuccessor relationships. This dependency ensures that the predecessor test case must be executed successfully before executing its successor. During execution, testers can automatically notify the execution assignees of successor test cases when their test cases are blocked or unblocked for executions. 

    • Introduced Test case and Test Execution dependency reports that showcase the dependency relationship between multiple test cases and their executions.

    • Project Administrators can choose to enable the feature for defining dependency relationships between test cases and configure the related execution settings. They can also opt to auto-propagate the execution status of predecessor test cases to successor test cases.

 

SCIM 2.0 Support for User Provisioning and Deprovisioning

  • QMetry now supports System for Cross-domain Identity Management (SCIM) 2.0, enabling seamless integration with identity providers, specifically OKTA, for automated user provisioning and de-provisioning. This feature ensures that only authorized users have access to QMetry, managed through a centralized user management process, maintaining compliance with security policies.

    • The following provisioning actions are currently supported: Push New Users, Push ProfileUpdates, and Push Groups.

    • Users will be automatically created and assigned to respective Projects and Roles when added to OKTA groups and automatically deactivated when removed from OKTA groups.

    • User attribute management, including modifying Username, First Name, Last Name, Alias, and Email ID, is also supported with this feature and can be made only through the identity provider platform.

    • Once SCIM 2.0 is enabled, user updates, creation, or deactivation, as well as project and role assignments, can only be done from the identity provider platform. Project Admins or other users with managing user permissions cannot make these changes directly withinQMetry.

​​
Risk-Based Analysis

  • Introduced the Risk-Based Testing feature to enhance the testing process by empowering testing teams to systematically identify, assess, and prioritize risks linked with requirements and test cases. This feature enables teams to focus their testing efforts on features with the highest likelihood of risks and potential defects.

    • Risk Definition: Project Administrators can activate the Risk-Based Analysis feature for their project. This functionality automatically creates the necessary risk fields and enables admins to define risks and other related factors, thereby ensuring comprehensive risk management.

    • Risk Association: Testers associate risks with requirements and test cases, assigning their likelihood and impact.

    • Determining the extent of testing: QMetry automatically computes the risk priority number and assigns the appropriate level of testing required for each risk.

    • Reports: Introduced Risk Traceability reports to assist testers in tracing risk factors associated with the requirements and their corresponding test cases, and vice versa.

    • To enable viewing risk-based fields in Jira, an install or upgrade of the QMetry Jira Integration latest app (v2.2.7) is required for the Jira Server and Data Center installations. For customers using Jira Cloud, the add-on will be auto-upgraded.

 

QMetry Intelligence (Only on Cloud)
Increase Testing Confidence with Flaky Score & Success Rate Metrics.

  • Flaky Score: QMetry Intelligence uses AI to assess the flakiness of test cases by calculating "Flaky Score" derived from their previous executions. This score empowers testers to identify test cases whose future execution result is non-deterministic. A flaky test case exhibits non-deterministic behavior when executed repeatedly under the same conditions, resulting in intermittent successes and failures. Identifying flaky tests is pivotal for maintaining control over testing processes, as they can impede testing pipelines and undermine confidence. Traditionally, determining test case flakiness requires manually comparing test results from multiple runs, which is time-consuming. With QMetryIntelligence, this is automated, saving testers and developers valuable time and effort. QA Managers can define and configure settings according to their specific testing processes for calculating the flaky score, aligning it with their unique testing methodologies.

  • Success Rate: Introducing the "Success Rate" metric for test cases, derived from their previous executions, that has significant importance in the testing process. For QA teams, the test case success rate is a crucial indicator for evaluating test case execution performance. A high success rate signifies a robust and dependable test case, providing confidence in its performance. On the other hand, a low success rate highlights potential issues or areas of improvement, signaling the need for further investigation and refinement.

 

Enhancements to Jira Integration

  • Project admins can now deactivate syncing for specific Jira System Fields within QMetry Requirements and Issues for selected Jira Issue Types. These fields include Description, Component, Fix Version, Priority, Labels, Attachments, Affected Version, Environment, and Assignee.

  • Project admins can now sync separate Jira Issue fields for viewing issue details in QMetry and creating issues from QMetry when configuring Jira Issue Types as QMetry Issues.

  • Users should upgrade their QMetry Exploratory Testing plugin to the latest version per the above enhancements and comply with QTM release 8.17. The latest versions of add-ons are as follows: Chrome 1.2.6, Firefox 1.1.0, and Edge 1.0.6.

 

Improvements to the Test Case Module

  • The latest execution status of a test case is now displayed on all Test Case List screens across the product. This status gives testers immediate visibility into whether a specific test case has been executed and displays its recent execution state. Project admins can configure parameters to tailor this display, allowing them to choose the display of the latest execution status based on the most recent execution within the current project or across projects. They can also decide whether to include only the recent or all the test case versions for determining the latest test case status.

 

Bug Fixes

  • Fixed a bug that prevented reordering linked test cases while creating a test suite.

  • Fixed a bug that prevented cloning projects containing test suites with cross-project test cases.

  • Fixed a bug that prevented filtering issues based on cycles within the issue module when a release has one of its cycles archived.

  • Fixed bug that displayed an incorrect message during login when a deleted user previously authenticated via SSO attempts to log in.

  • Fixed a bug that caused test cases export from a cloned project to display an incorrect username in the "created by" field.

  • Fixed a bug that prevented the display of the QMetry Test Case links in the Azure Work Item Links when test cases are associated with requirements from the details page.

 

Build 8.16.0.2 - Release Date: 2024-04-08

Summary: Bug Fixes

  • Fixed a bug that caused the first IDP-initiated SAML user login attempt to be redirected to the QMetry login page if the previous session had expired. 

  • Fixed a bug that caused the project name in the list values to be partially displayed when creating visual reports.

  • Fixed a bug that prevented all the previous test case versions from being displayed for linking while creating test suites.

  • Fixed a bug that failed the Test Execution details export to Excel (.xlsx) or CSV immediately if the user applied an empty filter on the execution tab.

  • Fixed a bug that prevented users with appropriate automation module permissions from scheduling automation agent commands, incorrectly requiring additional integration module permissions.

  • Fixed a bug that incorrectly triggered email notifications to unintended users for eSignature-enabled customers.

 

Build 8.16.0.1 - Release Date: 2024-02-26

Summary: Bug Fixes

  • Fixed a bug that prevented import of test cases from Excel/CSV files when the column mapped to the Summary field wasn't the first column.

  • Fixed a bug that exported test executions to Excel/CSV with incorrect test case and step details in some cases.

  • Fixed bug that exported requirements and test cases to Excel/CSV with data between HTML and Plaintext fields incorrectly interchanged.

  • Fixed bug for Firefox ESR v115.7.0 that did not retain the expanded folder structure and switched users back to the root folder on return.

  • Fixed a bug that caused the first IDP-initiated SAML user login attempt to be redirected to the QMetry login page if the previous session had expired.

 

Build 8.16.0. - Release Date: 2024-02-17

Summary: New Features & Bug Fixes

New Features
Automation Enhancements

  • Integrate Worksoft CTM to launch the execution of Worksoft Suites directly from within QMetry. After completion of the execution, view the test cases and their execution results in QMetry.

  • Automation test result upload for the JUnit framework will now mark the Aborted and Skipped execution statutes with their matching custom execution statuses within the project. If these matching execution statuses are unavailable in the project, the upload process marks the test executions as Failed and Not Applicable, respectively.

QMetry Intelligence Enhancements
Experience the future of testing today, powered by QMetry's AI-enabled product search! (Currently in BETA, Only for Cloud)

  • QMetry has introduced an innovative AI-enabled product search feature, revolutionizing testers' ability to inquire and discover answers within their project documents to meet their specific testing requirements. QMetry accomplishes this by enabling administrators to upload project-specific documents in multiple formats like PDF, Word, and Confluence public spaces.QMetry utilizes these documents for search to locate the precise answers, providing a powerful tool for testers. As an organization expands, it accumulates a vast repository of institutional knowledge and project-related information stored within various documents. To ensure the successful execution of critical projects, it becomes vital to empower testing teams with effortless access to information in project-specific documentation, fostering on-the-go learning and enhancing the efficiency of their testing processes.

  • Users can also utilize QMetry's inbuilt product search to ask questions about QMetry product features and receive answers from the product user guide. The revolutionary AI search explains features in a summarized format, offers step-by-step guidance for how-to questions, provides best practices from the extensive knowledge base, and expertly navigates troubleshooting challenges.

  • To activate the QI search feature on all users and projects, the super administrator should enable it for the QMetry instance. The project administrators can later enable the search feature on their projects by configuring their project-specific documents.

Report Enhancements

  • Export test cases linked to the test suite in PDF and Word formats for review or sharing purposes. Users can choose which test case and step fields to include in the export.

  • Administrators can now control user access to the Login Summary Dashboard by utilizing newly introduced distinct permissions.

  • The Test Execution Summary by Folder reports now include the Test Suite Summary columns in the drill-down view, accompanied by the Key. This enhancement enables testers to identify and distinguish between suites more effectively.


Issue Module Enhancements

  • For the QMetry Inbuilt Issue Module, now associate Issues with cycles along their respective releases. This capability enables users to efficiently monitor defects not tied to a specific test case or execution. Users will need to upgrade their exploratory testing plugin to the latest version to utilize the ability to associate issues created during testing with cycles.

  • Filter issues of Jira integrated projects based on custom fields when linking them to Requirements, Test Cases, and Test Executions.


Test Case and Test Execution Enhancements

  • On creating a test case from the requirement page, the user is now automatically navigated to the requirement's linked test case section, ensuring the focus remains on the requirement. The same flow is improved when creating a test case from the requirement list view.

  • Users can now view custom fields of test entities on the link screens. This feature allows testers to efficiently select test entities based on the combination and configurations of the customer fields, ensuring comprehensive coverage. The custom fields are available for display when linking requirements, test cases, test suites, and issues across the product.


Infrastructure Enhancements

  • The QMetry application is upgraded to Tomcat 10, enhancing security and reliability. 


Bug Fixes

  • Fixed error displayed in Jenkins logs when importing the automation test results and monitoring the completion status.

  • Fixed a bug that prevented the menu search from functioning correctly.

  • Fixed a bug that caused intermittent syncing issues in the custom report module for cloud subscriptions.

  • Fixed permission warning displayed to the users with adequate rights when navigating to the comments section or performing export or bulk operations in the Issue module.

  • Fixed permission warning displayed to the users with adequate rights when navigating the execution screen.

  • Fixed bug that prevented renaming X and Y-axis labels in custom reports through chart settings.

  • Fixed a bug that prevented filtering test cases based on a folder while linking to the test suite when the search criteria contained folders preserved from the last search.

  • Fixed a bug that prevented the export of test executions in PDF and Word formats.

  • Fixed a bug that prevented the display of cross-project test case executions and issues in the traceability report.

 

Build 8.15.0.3 - Release Date: 2024-01-24

Bug Fixes

  • Fixed a bug that prevented users from setting assignee for issues in projects integrated with Azure DevOps. 

  • Fixed a bug that caused slowness while updating Actual Outcome and Comments on the test execution screen for test cases containing a large number of steps.

 

Build 8.15.0.2 - Release Date: 2023-12-01

Bug Fixes

  • Fixed a bug that prevented users from being able to view test suites in the test suite module if the project name gets changed.

  • Fixed a bug that caused the attachment thumbnails to appear blurred and with occasionally displaced image within the thumbnail.

  • Fixed a bug that caused the removed comment on the test execution screen to reappear and prevented testers from resetting the comment field to empty.

  • Fixed a bug that prevented test steps from loading after clearing the applied sorting in the test execution detail view unless the user switched tabs or reloaded the page.

 

Build 8.15.0.1 - Release Date: 2023-11-20

Bug Fix

  • Fixed a bug that prevented syncing some Jira Issues with the QMetry Issues Module automatically or when force synced.

 

Build 8.15.0 - Release Date: 2023-11-04

New Features, Enhancements & Bug Fixes

New Features
New Features in Automation

  • Integrate seamlessly with Azure DevOps and GitLab pipelines to upload automation results.

  • New Features in Automation Agent -

    • Operate the Automation Agent on Windows, Linux, and Mac OS through the command line interface.

    • Open APIs are now available to schedule, execute, view the status, and download logs of the Automation Agent.

    • Introduced a manage schedule option for the agent, which allows users to alter the scheduled time and execution commands for the run later or recurring triggers.


New Features in Issue Module

  • Auto-generate a two-level folder hierarchy based on Jira fields to facilitate the automatic organization of synchronized requirements from Jira.

  • Introduced support for Jira Sub-Task issue types :

    • Sync Jira sub-task issue types as Requirements or Issues. The requirements and issues synced from Jira now display their respective subtasks in a dedicated new section.

    • Create Jira sub-task issue types as defects for failed executions. The Exploratory Testing Add-ons now support creating sub-task issue types as defects for failed executions.

  • Perform bulk export of all issue details, including their comments in wiki format, from QMetry's inbuilt issue module.


New Features on Collaboration

  • Improve collaboration by tagging your fellow team members in the comments to send them instant email notifications.

  • Easily share a Requirement, Test Case, Test Suite, Test Execution, and Issue link with other users using the following options -

    • Copy a direct link generated using the share feature on the detail screen.

    • Send an email with a custom note using the share feature on the detail screen.

    • Generate the URL with the format <https://<URL>>/#/<AssetType>/<AssetKey>.


New Features in Reports

  • Drill down into custom reports created using Visual Reports by clicking the counts to view detailed information about the records in the gadgets and export the view in CSV, except for cross-table charts.


New Features in Customization

  • Project administrators can now configure default values for system-defined fields separately for every module.

  • Copy or Import Platforms and their associated attributes along with their lists, System and Custom-defined list values, and Labels from one project to another.


Miscellaneous Improvements

  • The folder tree structure for every module now retains the user's recently expanded folder hierarchy while navigating between modules or projects or during screen refresh.

  • The count of assets in the folder hierarchy is displayed next to each folder for quicker reference.

  • Empty filters applied to QMetry-specific fields on the Requirement, Test Case, Test Suite, and inbuilt Issue modules are now preserved based on user preferences when clicked on save and apply button to make search efficient and eliminate the need to re-enable these filters each time.

  • The Test Suite's Test Execution section allows users to rearrange, show/hide, and expand columns. The user's view gets preserved, and the same view is displayed while generating the traceability report on test executions and performing bulk operations on eSignature-enabled projects.


QMetry Jira Integration App Updates

  • Release 8.15.0 upgrade requires an install/upgrade of the QMetry Jira Integration app latest v2.2.6. For customers using Jira Cloud, the add-on will be auto-upgraded.

  • QMetry Jira Integration app v2.2.6 is compatible with Jira Server/DC v9.11.


Bug Fixes

  • Fixed bug that prevented test steps update while unlinking and linking shareable test steps simultaneously.

  • Fixed a bug that appended the test case/step summary of automated test cases created through Junit automation upload with '()' at the end.

  • Fixed a bug that appended the test case/step summary of automated test cases created through Junit automation uploads with a dot at the beginning when the class name does not exist.

  • Fixed bug that prevented the drill-down on the 'Planned Requirements Summary Report'.

  • Fixed bug that prevented the display of the section 'Execution Details Test Suite wise' in the 'Test Execution Summary by Folder Dashboard'.

  • Fixed a bug that displayed duplicate 'Total Test Case Executions' and 'Total Unassigned Test Case Executions' columns in the Test Suite module arrange columns option.

  • Fixed bug that prevented archiving the projects set as default logged-in scope for deactivated users.

  • Fixed a bug that prevented cloning the projects with test cases containing custom fields in test steps.

  • Fixed bug that prevented displaying an appropriate failure reason on the scheduled task and logs for test suites import failure.

  • Fixed bug that prevented deletion of attachments on the execution screen for users with sufficient permissions.

  • Fixed bug that allowed the creation of users more than the license limit, preventing users from logging in to QMetry for concurrent licensing type.

 

Build 8.14.0.5 - Release Date: 2023-10-20

Bug Fix

  • Fixed a bug that prevented data searching in the Test Case module through the 'Ask Me Anything' search box.

 

Build 8.14.0.4 - Release Date: 2023-09-06

Bug Fixes

  • Fixed a bug that prevented syncing issues from Jira cloud to QMetry for newly integrated projects or when manually syncing existing integrated projects.

  • Fixed a bug that prevented users from editing custom gadgets and adding them to the dashboard when shared with co-ownership by the system administrator.

  • Fixed a bug that prevented the export of Test Suite custom fields in the PDF and Word export of Test Execution details.

  • Optimized internal queries that sync custom reports data based on event logs to resolve issues that intermittently stopped syncing some QMetry records to custom reports.

 

Build 8.14.0.3 - Release Date: 2023-08-28

Bug Fix

  • Fixed a bug that prevented the export of Test Suite executions in CSV/Excel with the correct sequence of test case steps.

 

Build 8.14.0.2 - Release Date: 2023-08-21

Bug Fixes

  • Fixed a bug that prevented the display of issues linked to test execution in the test case issues tab when the test case and test suite belonged to different projects.

  • Fixed a bug that prevented syncing of Jira custom fields in the requirements and issues module when the value of the field type list is deselected and set to empty in Jira.

  • Fixed a bug that prevented syncing updates made to Jira custom fields of the field type list in the QMetry Insights module, specifically when assigning a value to an initially empty value.

  • Fixed a bug that caused a disruption in the connection between Jira and QMetry when any of the Jira apps were uninstalled or disabled.

 

Build 8.14.0.1 - Release Date: 2023-08-14

Performance Bug Fixes

  • Fixed a bug that was causing slowness while fetching the available issues to be linked on the execution screen.

  • Fixed a bug that was causing the test suite module grid to become unresponsive for projects having too many releases and cycles.

 

Build 8.14.0 - Release Date: 2023-08-05

Improvements & Bug Fixes

Improvements

  • QMetry has upgraded its database to MySQL v8.0.33, resulting in improved performance, enhanced security, and increased reliability.

Bug Fixes

  • Fixed bug that caused auto-capitalization of text in the step details recorded for an exploratory session.

  • Fixed bug that prevented removing gadgets "Issue Velocity Compared To Test Cases Executed" and "Issue Velocity Compared to Requirements" from a custom dashboard.

  • Fixed a bug that prevented displaying controls to add/delete rows and columns in tables within the description fields.

 

Build 8.13.0.1 - Release Date: 2023-07-22

Bug Fixes

  • Fixed a bug that prevented viewing and downloading certain older attachments on the test execution screen.

  • Fixed a bug that prevented the display of some older images in the test step details and caused an error when updating the test case.

Build 8.13.0 - Release Date: 2023-07-01

New Features, Enhancements & Bug Fix

New Feature

Launch CI/CD pipelines from within QTM

  • With continuous testing, CI/CD pipelines today are responsible for multiple tasks, including test execution. Integrate QTM with your preferred CI/CD platform, such as Jenkins, Bamboo, Azure DevOps, GitLab Runners, GitHub Actions, and Circle CI, to trigger automated testing pipelines with a single click. Now, testers can save and launch remote CI/CD pipeline jobs directly from QTM. Testers can select and map a configured rule to a test suite, then trigger the pipeline job and automate the uploading of the results after successfully executing the job. This feature enables all testers to participate in test automation and also reduces the overhead of navigating between multiple tools by automating the testing process and reporting results.

Enhancements to Test Execution

  • Introduced a timer (stopwatch) for testers to automatically record the time taken in minutes to execute the test case; to accurately measure the actual test execution duration.

  • The Test Suite - Test Case tab now displays an indicator to help testers quickly identify parameterized test cases that do not have data values assigned for executions.
    @ Blue Color - Indicates parameterized test cases that do not have data values assigned for executions.
    @ Green Color - Indicates parameterized test cases having values assigned for all parameters.

  • Unlinking of the Release/Cycle or Platform associated with closed test executions is restricted for eSignature-enabled projects to prevent accidental unlinking and preserve the test execution records.

Introducing Co-Ownership for Custom Dashboard and Gadgets

  • Introduced an ability for owners to share custom gadgets and dashboards with edit permissions; by appointing others as co-owners.

  • The super administrator can now view the list of all custom dashboards and report gadgets created by any user in the system and share or assign other users as co-owners, individually or in bulk.

  • While deactivating a user, the administrator can now assign another user as co-owner of the gadgets and reports owned by the user getting deactivated.

Enhancements to Attachments

  • Inline Attachments - Add inline images to textboxes using the copy & paste; click to view them.

  • Attachment Section -

    • Introduced a new thumbnail (strip) view that displays the preview of Attachments; click on the images and files under the Attachments to view them without downloading them.

    • Preview uploaded images while submitting them on the add attachments window.

Miscellaneous Improvements

  • Introduced a button to keep the menu panel expanded/collapsed while navigating around modules & pages.

  • Introduced a user setting to toggle the auto-pop-up behavior of the QQBot suggestion window allowing users to customize their preferred experience with the bot while viewing the predictions.

  • The issue status is now displayed at the top of the issue details screen, alongside the issue key, making it easier for users to focus on it when viewing the complete details.

  • The Test Executions export for an eSignature-enabled project in PDF or Word now includes the approval details of the Test Cases.

  • The Test Case and Execution export in PDF now supports both landscape and portrait orientation modes. The report header on each page contains the Logo, Background, Project Name, Report Name & Exported Time.

Enhancements to Jira Integration

  • The QMetry section within the Jira story and bug page now displays the Owner, Category, and Labels for linked test cases, along with other relevant test case fields providing comprehensive information about the test cases.

  • Release 8.13.0 upgrade requires an install/upgrade of the QMetry Jira Integration app latest v2.2.4. For customers using Jira Cloud, the add-on will be auto-upgraded.

  • QMetry Jira Integration app v2.2.4 is compatible with Jira Server/DC v9.9.0


Bug Fixes

  • Fixed a bug that allowed unsupported Jira field types to be available for mapping in the Jira field configuration settings; this prevents users from selecting the unsupported field type.

  • Fixed a bug that prevented syncing the latest test execution comment to QMetry Insights reports.

  • Fixed a bug that did not allow uploading SAML metadata files larger than 10kb; this prevented configuring SSO for authentication.

  • Fixed a bug that displayed archived releases and cycles on the test cases and requirements link screens.

  • Fixed bug that resolves issues for the queries written with substring functions by upgrading the internal reports library.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Related pages

What's New
What's New
QMetry Test Management v8.19.0
Read with this
Release Notes
Release Notes
QMetry Test Management Server v8.18.x
Read with this
QMetry Test Management Apps
QMetry Test Management Apps
QMetry Test Management v8.19.0
Read with this
Supported Environments
Supported Environments
QMetry Test Management v8.19.0
Read with this
Release Notes
Release Notes
QMetry Test Management for Jira DC 4.10.x
Read with this
Connect Jira to QMetry Using OAuth
Connect Jira to QMetry Using OAuth
QMetry Test Management v8.19.0
Read with this

Back to QMetry All Products Help Page