Release Notes

Build 8.17.1 - Release Date: 2024-08-08

Summary: New Features, Improvements & Bug Fixes

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.

QMetry Jira Integration App Update - Version 2.2.8

Updated QMetry Jira Integration app v2.2.8 is released, which addresses security vulnerabilities in two libraries used by the Jira app. This update is recommended and compatible with QMetry Application v8.17.0 and above.

 The update addresses the following vulnerabilities:

• CVE-2022-42003: Uncontrolled resource consumption vulnerability in the Jackson-databind library.

• CVE-2023-24998: Denial of service vulnerability in the commons-fileupload library.

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

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

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

• 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.16.0.1 - Release Date: 2024-03-07

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.

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. For server customers, the release upgrades include the QMetry application bundled with Tomcat10 as the default configuration.

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

• 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 a bug that exported requirements and test cases to Excel/CSV with data between HTML and Plaintext fields incorrectly interchanged.

• Fixed a 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.15.0.3 - Release Date: 2024-01-25

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

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 images 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-Release date: 2023-11-15

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.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-09-04

Improvements & Bug Fixes

Improvements

• The latest QMetry release, v8.14.0.3, now supports MySQL v8.0.33 database as the default option for installation and upgrades. The earlier QMetry versions are on MySQL v5.7.29 database. With the release of v8.14.0.3, support for QMetry on MySQL v5.7.29 has been discontinued, making it mandatory for all our customers to upgrade to the latest version, v8.14.0.3. This upgrade is essential because future QMetry releases will support only MySQL v8.0.33. QMetry recommends that server customers upgrade to v8.14.0.3 and utilize the included support for MySQL v8.0.33, which provides improved performance, enhanced security, and increased reliability. For any assistance or queries regarding the upgrade, contact QMetry Support.

• QMetry v8.14.0.3 installation is compatible with IPv4 and IPv6, ensuring seamless connectivity and support for both traditional IPv4 networks and the newer IPv6 networks.

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

• QMetry Jira Integration app v2.2.5 is compatible with Jira Server/DC v9.10.0

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.

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

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

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

Build 8.13.0.1 - Release Date: 2023-07-27

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

New Features, Enhancements & Bug Fix

New Features

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

Enhancements to eSignature workflow

• Introduced an option to turn off the Approval workflow for test suite executions in the eSignature-enabled projects; with the approval workflow turned off, executions would be system approved by default and ready to execute. The Closure workflow will be in place as before.

• Uploading automation results would require only automation permissions, and users would no longer need Test case & Test Suite Execution permissions for the last approval level.
  
  
  

Improvements to Automation Test Result Imports 

• Improved performance for automation test results imports using Automation API, QMetry Test Management Plugin for Jenkins, QMetry Test Management Plugin for Maven & QMetry Bamboo Integration app.

• The automation result import process now reuses the existing test case version for which the summary and steps match exactly when the test case has multiple versions.

• Introduced a new parameter "is_matching_required" that allows updating execution status on a linked test case version or latest version by matching test case keys in the result file; instead of creating a new version even if the test summary and steps do not match.

• New test suites can be created in a specified folder while importing automated test results using the "tsFolderPath" parameter.

• The job status and the test suite details of the automation test result imports are now visible in the scheduled tasks section.

• The "test suite key" parameter will no longer be available directly in the automation API response. The automation API response will now provide a "request-id" parameter. A followup API using the "request-id" parameter will return the test suite key and import status. For more details, refer to the API changes section.

• The Description value in the result file for the Cucumber framework will be imported as a Test Case Description when a new version of a test case gets created.

• Added support for importing test case step attachments for the QAF framework.

• Reusing existing test cases is supported using the entity key for the Junit framework.

• For the QAF framework, attachments associated with sub-checkpoints are uploaded to their respective test case steps when uploading automation results.

• For QMetry projects using the internal issue module, the "Error message" and "Trace" for the automated test executions get added as a text attachment to the bug for developer reference.

• Skip status in the automation result file is applied as "Not Applicable" instead of "Not Run" for automation test executions upload.

• Achieve traceability by auto-linking internal requirements with Junit test cases uploaded through automation import using the keyword "requirementEntityKey" to specify the entity key in the result file.

• Achieve traceability by auto-linking requirements synced from external trackers (e.g. Jira, Azure, Rally) with Junit test cases uploaded through automation import using the keyword "requirementExternalKey" to specify the external issue/work item key in the result file.

• Allow specifying of multiple values to "requirementExternalKey", "requirementEntityKey", and Testcasekeys attribute in the Junit result file to link/map multiple requirements to test cases.

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.

Build 8.12.3.2 - Release Date: 2023-05-22

Enhancement

• Minor enhancement for an internal migration script, there is no direct impact to customers.

Build 8.12.3.1 - Release Date: 2023-04-24

Enhancements, Compatibility & Bug Fixes

Enhancements

Administrative Enhancements

• The system administrator can now set a time interval for inactive user sessions to log out automatically.

• The system administrator can now configure the organization's logo to the PDF and Word exports for test executions, test cases, and reports and as well as to the email notification template. The system administrator can also permit the project administrators to configure their project logo for the PDF and Word exports for the project.

• Organizations can now configure the audit/change log's retention period of up to 3 years for compliance requirements.

• New projects can have keys that are up to 10 characters long.

Reporting Enhancements

• QMetry Insights now allow the creation of visual and advanced query reports using group by function on custom fields.

• Export the test case and the test execution details to Word for sharing audit and compliance documentation.

Jira Integration Enhancements

• QMetry section inside the Jira story page now displays the Test case execution summary with multiple filters to drill down into summary progress.

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

• QMetry Jira Integration app v2.2.3 is compatible with Jira Server/DC v9.7.0.

Execution Enhancements

• The test suite list view and the test execution section inside the test suite now display the total counts of planned and unassigned test case executions, making it easier for teams to review the test execution assignment status.

Security Enhancements

• QMetry URL now includes security headers such as referrer policy, content security policy and permissions policy.

Bug Fixes

• Fixed a bug that prevented already scheduled custom dashboards from being triggered at the designated time due to daylight savings time changes.

• Fixed a bug that prevented generating custom reports containing the users' table without adding a mandatory project filter.

• Fixed bug that displayed the list values partially while selecting them under advanced filters on list view screens.

• Fixed a bug that caused a project clone initiated with the folder structure option to fail due to an incorrectly checked condition.

• Fixed a bug that incorrectly displayed archived test executions in the Test Executions Approval report for an archived test suite.

Build 8.12.1.1 - Release Date: 2023-02-20

Enhancements & Bug Fixes

Enhancements to the Test Execution Screen

• Introduced a comprehensive dialogue-based "Detail" view of the test execution screen that displays complete details for a test case execution in a more structured way, making it easier for testers to access all the information they need on a single screen. The new view displays details grouped under seven tabs that can be re-ordered, a better layout for step executions, and a consolidated view of the audit history for each test case execution run.

  • Users can choose between the Default (old) or Detail (new) view according to their preference.

  • The newly introduced "Details" tab displays all test case fields without the tester having to navigate to each test case separately.

  • Introduced the "List" and "Grid" views for displaying test step details. Users can choose either view according to their preference.

  • With the newly introduced "Requirements" tab, testers can view requirements associated with the test case under execution.

  • The newly introduced "Attachments" tab displays a consolidated list of attachments added while authoring or executing a test case/step.

  • The newly introduced "Audit log" tab displays test results and change logs separately for each test case execution.

• Comments on Test case execution now allow adding multiple comments by auto-capturing the Username and DateTime stamp.

Enhancement to the Automation Agent

• Trigger and Schedule the automation commands through the Automation Agent from inside the Test Execution.

  • Save the parameterized command in the system-defined field "Automation Script Execution Command" in the Test Suite details. The Automation Agent will trigger and execute the script saved in this field by replacing parameters with values selected in the test suite details.

• The limit of triggering a command through the Automation Agent increased from 255 to 5000 characters.

• A new version of Automation Agent (v8.12.1) compatible with QTM v8.12.1 is available.

Enhancements to Advanced Reporting

• Create custom reports containing fields of external trackers (like Jira, Azure or Rally) synced with the QMetry projects. System administrators can configure settings to display these external trackers fields in the QMetry Insights - Visual Report entities and Advanced Query Report tables.

Bug Fixes

• Fixed bug that prevented displaying Issue Average Aging graph when the report is filtered based on Issue Priority.

• Fixed bug that prevented displaying count for unresolved issues in the Issue Average Aging Report.

Build 8.12.0 - Release Date: 2023-01-11

Enhancements & Bug Fixes

Enhancements to the Test Cases Module

• Enabled creation of the shareable test cases from steps containing data parameters. Shareable test cases with parameterized test steps will refer to the test data specified for the main test case during execution.

• Link defects directly to a test case from the issue section in the test case details. Earlier testers could link defects with test cases through the test execution screen only. The following changes to these features and modules will be applicable:

  • Issues linked directly to the test cases will be auto-linked to the associated requirements of the test case and displayed under the Issue Links section of the Jira page for Jira issues synced as Requirements.

  • Jira issues linked directly to the test cases will display test case details in QMetry's Test case section on the Jira page.

  • Reports - Requirement With or Without Issues, Test case With or Without Issues & Resolved Issue Verification will include the defects linked directly to the test cases.

  • New fields and tables introduced to the Visual/Advanced Query Report module enable the creation of reports containing defects linked directly to the test case or execution screen. Refer to the updated entity relationship diagram for more details.

  • With release 8.12.0, creating a new visual report using fields only from the test case and issue entities will display defects linked directly to the test cases. Creating visual reports that show data on execution defects will require adding fields from all three entities - test cases, issues, and execution. Refer to this blog for the changes to the existing visual reports.

• The Issues section in the test case will display distinct defects linked directly or through test execution. Clicking the execution count will display associated test execution details like the test suite key, summary, release, cycle, platform, build and execution status.

Enhancements to Issue Module

• QMetry's internal issue tracker will display the Associated Releases in the list view and allows filtering issues on the Associated Releases field.

Bug Fixes

• Fixed bug that prevented recording of step numbers in the change log for updates to step execution details on the execution screen.

• Fixed bug that incorrectly activated user despite selecting No on the activation confirmation pop-up.

• Fixed bug that prevented users from changing the mapped folder configured to import Jira issues into QMetry as Requirements.

• Fixed bug that prevented generating the test execution summary by folder report for some projects.

• Fixed bug that prevented users from archiving list values associated with other projects from the current project.

Build 8.11.2 - Release Date: 2022-11-15

Enhancement & Bug Fixes

Enhancement

• Updates to Spark v3.3.1 and JDK v17 in QMetry Insights fix a potential data sync failure caused by a bug in the older spark version.  

Bug Fixes

• Fixed a bug that prevented the loading of test cases in Jira's QMetry test case panel if the test executions were large in number.

• Fixed a bug that prevented displaying user-defined fields in visual reports.

• Fixed a bug that exported test case step executions in an excel or CSV file displaying an incorrect count of defects linked.

• Fixed a bug that prevented syncing Jira stories to the Requirement module for a project integrated with multiple Jira projects by a user that got deactivated later.

• Fixed a bug that displayed an error requiring incorrect build permission while loading the issues and the combined view tab for a requirement.

Build 8.11.0 - Release Date: 2022-10-14

Improvements, Enhancements & Bug Fixes

Improvements & Enhancements

Reporting and Dashboard

• Introduced Planned vs Actual Execution analysis gadget under the Test Execution Summary report to help QA managers understand the current and expected execution rate to meet the release timelines.

• Export complete test execution details in a PDF as audit and compliance evidence. Organizations that have subscribed to the Integration app will get an option to export execution details in a pdf.

• Dashboard gadgets will always display the counts or percentages without a need to hover.

• Dashboard gadgets will preserve the user's preferred graphical or chart data report view. Shared dashboards and PDF export will display the gadget's view according to the owner's preference.

Issue Module

• Attach images/files while creating defects under projects using the internal issue module.

• Add multiple attachments while creating a defect in the integrated external trackers (e.g. Jira, Azure or Rally) from within QMetry.

Change Log

• The change log highlights the difference between old and updated values to make it easier for users to understand the updates.

• Change logs record detailed step-level updates when creating a new version of the test case.

eSignature

• Introduced email notification settings for eSignature-enabled projects to allow project administrators to enable or disable forced notifications on events like review, approval, closure, or a request change.

• Administrators can add up to 50 reviewers and approvers at all levels for an eSignature-enabled project.

• The email notifications on review, approval, closure and request change will contain the asset summary along entity key for easy identification.

Miscellaneous Improvements

• Sync the latest version of the requirement to its linked test cases individually or in bulk using the new "Sync Latest Version of Requirement" option on the requirement screen > test cases tab.

• Sync the latest version of the test case to its linked requirements individually or in bulk using the new "Sync Latest Version of Test Case" option on the test case screen > requirements tab.

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

Bug Fixes

• Fixed bug that prevented a review of requirements due to an incorrect status applied by bulk edit operation in an e-Signature enabled project.

• Fixed bug that prevented the display of requirements in a project having a user-defined field with the same name as the system field.

Build 8.10.3.1 - Release Date: 2022-07-30

Bug Fixes

• Fixed a bug that prevented copying data with tables and hyperlinks into comments and the actual outcome field on the execution screen.

• Fixed a bug that prevented access to the issue module for some projects due to duplicate epic links.

• Fixed a bug that prevented seamless syncing between Jira stories and QMetry requirements for some projects due to the duplication of some synced issues.

• Fixed a bug that delayed syncing updates from Jira/Azure to QMetry.

• Fixed a bug that gave an error while cloning projects that contain a large number of test executions.

• Fixed a bug that did not fetch all test cases created through Automation API (apiVersion=1) when filtered by "Testing Type".

• Fixed a bug that prevented users having the default QA Manager role from creating a defect into Azure.

• Fixed a bug that did not preserve HTML formatting of Jira descriptions synced to QMetry.

• Fixed a bug that prevented an appropriate error from being displayed when creating issues with descriptions longer than 65553 characters.

Compatibility JIRA Improvements

• `QMetry Jira Integration` app v2.2.0 is released compatible with Jira Software v9.0 and v9.1. Customers hosted on the Jira server/data center will need to update the app manually. 

Build 8.10.3 - Release Date: 2022-06-24

Improvements & Bug Fixes

General Improvements

• QMetry v8.10.3 upgrades all third-party libraries used internally to their latest version making QMetry more secure by removing any existing vulnerabilities.

• Improved UI experience - QMetry web application upgraded with a new version of Angular framework 13.

• QMetry installation is now compatible with Open JDK 17.0.2 & Apache Tomcat 9.0.62.

• QMetry upgrade to v8.10.3 will update the Open JDK to 17.0.2.

• A compatible version of Automation Agent 8.10.3 is available with this QMetry upgrade to v8.10.3. The latest agent supports only Open JDK 17.0.2. Users should upgrade the JDK & Automation Agent post-upgrade. 

Bug Fixes

• Fixed a bug that displayed list values from the current project instead of the selected project after sorting list values while editing the user-defined fields.

• Fixed a bug that prevented unlinking platform from a test suite associated with too many platforms and test cases.

• Fixed a bug that prevented some users from accessing test case folders within a cloned project.

• Fixed a bug that prevented searching users in the user list while sharing custom report gadgets and dashboards.

Build 8.10.0 - Release Date: 2022-03-17

Improvements & Bug Fixes

Miscellaneous Improvements

• The value of the estimated time field on the test case detail screen now accepts up to 99999 minutes.

• Added option to select/unselect all fields on the arrange column menu in the list grids.

• Release 8.10 upgrade requires to install/upgrade the latest version v2.1.8 of Jira Integration - QMetry Enterprise App in Jira. For customers using Jira Cloud, the add-on will be auto-upgraded.

Bug Fixes

• Fixed bug that changed the execution type of manual test execution to automated on the execution screen after manual sync of the latest test case version.

• Fixed bug that prevented navigating backwards on test case steps using shift-tab keys. 

• Fixed bug that allowed updating a sharable test case on the same version for an eSignature enabled project.

• Fixed bug that did not show the screenshots in the comments section of issues synced from Jira.

• Fixed a bug that prevented configure of SAML IDP metadata XML file on offline docker installation.

• Mitigated - Apache Log4J Security vulnerability - CVE-2021-45105 by replacing the Log4j2 libraries with version 2.17.0 on the QMetry report server.

Build 8.10.2 - Release Date: 2022-05-18

Improvements & Bug Fixes

Improvements

Improvements to eSignature & Part 11 compliance 

• Introduced multilevel closure workflow for test execution runs.

•  

  • The closers' user list has been separated from the approvers' list to facilitate the change with this release. The closure workflow will have a new level containing users copied from the final approval workflow level.

  • Added a bulk operation to request a change on test run executions having closures initiated to allow changes before final closure. 

• SAML users can now authenticate assets for Part 11 enabled projects using an authentication token.

• QMetry & LDAP users can now alternatively authenticate test assets for Part 11 enabled projects using an authentication token with settings enabled by the super admin.  

• Administrators can set up to 30 reviewers and approvers at all levels for an eSignature enabled project.

General Improvements 

• For the QAF framework, the attachments associated with sub checkpoints are uploaded to their respective test case steps when uploading automation results.

• For QMetry projects using the internal issue module, the "Error message" and "Trace" for the automated test executions get added as a text attachment to the bug for developer reference. 

• Skip status in the automation result file will be applied as "Not Applicable" instead of "Not Run" for automation test executions upload.

• The total execution count for the test case gets displayed under the 'Test Case' panel in Jira. 

• Release 8.10.2 upgrade requires an install/upgrade of the latest version v2.1.9 of the QMetry Jira Integration app. This version is compatible with Jira software v8.22. 

• Improved UI experience - QMetry web application upgraded with Angular framework version 13. 

Bug Fixes

• Fixed a bug that reset the current folder selection to the root folder post performing bulk operations or moving/copying assets.

• Fixed a bug that prevented displaying test cases for bulk operations when moved/copied to an eSignature enabled project.

• Fixed a bug that prevented displaying attachments and bugs on closed test executions for an eSignature enabled project.

• Fixed message tip on execution screen to guide testers to map missing parameter values for parameterized test cases.

• Fixed a bug that prevented importing automation result file of Robot framework that did not contain test case steps.

Build 8.9.0.5 - Release Date: 2022-02-08

Miscellaneous Fixes

• Compatibility changes specific to Jira API authentication.

• Fixed a bug that prevented the upload of attachments with file extensions .7z, .log, .py (python) and .ps1 (PowerShell).

Build 8.9.0.3- Release Date: 2021-12-30

Bug Fixes