Release Notes 8.18.x

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:

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.

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:

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.

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.

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.

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.

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.