Release Notes
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.
Previous Versions