Release Notes 8.13.x

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.

With continuous testing, CI/CD pipelines today are responsible for multiple tasks, including test execution. Integrate QMetry 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 QMetry. 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.

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 or Cycle or Platform associated with closed test executions is restricted for eSignature-enabled projects to prevent accidental unlinking and preserve the test execution records.

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.

Inline Attachments - Add inline images to textboxes using the copy and paste. Click to view them.

Attachment Section

Introduced a button to keep the menu panel expanded/collapsed while navigating around modules and 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 and Exported Time.

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

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.

Improved performance for automation test results imports using Automation API, QMetry Test Management Plugin for Jenkins, QMetry Test Management Plugin for Maven and 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 case

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.