Back to QMetry All Products Help Page
Release Notes
- Mrunalini Potnis
- Niharika Choudhury
- Rachit Kacheria (Unlicensed)
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.
Previous Versions
Back to QMetry All Products Help Page