Build 8.17.1 - Release Date: 2024-08-08 Summary: New Features, Improvements & Bug FixesReport 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: 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-12Summary: New Features, Improvements & Bug FixesNew Features Test Case Dependency 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.
|