QMetry Test Management for Jira Cloud 4.13.1 Release Date: 2025-03-15 Summary: New Features, Enhancements, and Bug Fixes New Feature Design Test Cycles with QI (Currently in Beta, Only for Cloud) Introducing Design Test Cycles with QI, an AI-powered feature that transforms test cycle creation. QI analyzes your execution objectives to deliver precise recommendations for relevant test cases, ensuring thorough coverage and efficient planning. This feature empowers teams to enhance test coverage, speed up cycle creation, and manage complex testing across projects. Key Features: AI-Powered Recommendations: Tailored test case suggestions aligned with your objectives. Cross-Project Search: Quickly find relevant test cases across multiple projects. Customizable Test Cycles: Control your test cycles through manual selection and automated sorting based on priority or QI recommendations. Elevate your testing process today! Watch Video: Create New Test Cycles New Enhancements for Auto-Generate Test Cases using QI (Currently in Beta, Only for Cloud) Enhance your testing process with QI-driven test case generation, enabling you to create comprehensive test cases more efficiently. By leveraging an existing test case as a reference and incorporating user-provided instructions, QI intelligently generates new test cases, ensuring improved test coverage and alignment with evolving requirements. Whether you need to create a new test case, update an existing one, or refine specific test steps, QI streamlines the process while preserving relevant details. Bug Fixes Fixed a bug that prevented error logs from being displayed in a readable format for test cases uploaded via automation. Fixed a bug that added extra space to QMetry gadgets on the Jira dashboard when refreshed. QMetry Test Management for Jira Cloud 4.13.0 Release Date: 2024-12-21 Summary: New Features, Enhancements, and Bug Fixes New Feature Display Theme for QTM4J
QTM4J now supports Dark, Light, and Match Browser themes, automatically aligning with Jira user preferences for a consistent experience. The dark theme enhances usability and comfort in low-light environments. New AI Features for Auto Generate Test Cases using QI (Currently in Beta, Only for Cloud)
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 summary and expected results for content enhancement. Testers can enhance and refine the content using the following in-built options, depending on their specific needs: Regenerate Text: QI will rewrite the content for improved clarity or structure. Suggest Alternatives: QI will provide alternative phrasing or wording options to enhance the content. Add More Details to Text: QI will expand the content by including additional information or context. Summarize Text: QI will condense the content into a shorter, more concise form while retaining key details. Ask QI: Additionally, testers can prompt QI with specific commands such as EnrichVocabulary, Adjust Tone (e.g., make it more formal or professional), Simplify Text, Proofread Text (e.g., check and correct grammar, spelling, and punctuation errors), Refine the Text, or Make it More Engaging. Note: This feature generates text-based content only. It does not support or process input containing inline images, tables, URLs, rich text formatting, code blocks, certain ASCII characters, videos, or attachments. Import Test Cases from Cucumber-Gherkins BDD Feature Files
Testers can now import functional test cases seamlessly from the Cucumber-Gherkins BDD feature. It saves significant time and effort, enabling teams to align their testing workflows with Agile and BDD practices. This feature is accessible from the following screens: Jira Requirement (Story) Page: Initiate test case creation from the BDD Panel using feature files synced from source code repositories or saved within the inbuilt BDD editor. Test Case Module: Import multiple feature files directly from the module. Test Case Details Page: Import individual scenarios within a test case as test steps. Key capabilities include: Import Scenario, Scenario Outlines, Examples, and Rules seamlessly. Use test case key tags to update existing test cases or create a new version, and story key tags to link test cases with requirements. Automatically convert tags into Labels, assigning them to corresponding test cases. Utilize 'Examples' from scenario outlines as test case parameters. Imports initiated from the Requirement or Test Case modules run in the background. Testers can monitor the import status and access detailed logs to review failures or warnings. Copy/Import QTM4J Project Setup
Jira Administrators can now simplify project setup by copying QTM4J Project Settings, Permissions, and Configurations from one project to multiple projects. Similarly, Project Administrators can import these settings from any project into the current project. This feature eliminates manual replication of settings, enabling administrators to use a project as a template. Administrators can choose to copy all settings or select specific configurations from the source project. The copy/import project settings process runs in the background. Administrators can access the status and detailed request logs to review failures or warnings. The copy process automatically skips duplicate fields and archived values, ensuring a clean and consistent configuration. Offline Execution for Test Cycles
Testers can now execute test cases offline and upload the results to their respective test cycles. This feature enhances flexibility and productivity for teams working in environments with limited or no connectivity. Key highlights - Export Capability: Test cycles, with their associated test cases and steps, can be exported from the test cycle module to an Excel file for offline use. Offline Execution: Testers can update execution results and related test execution fields for both test cases and steps directly in the exported Excel file. Re-import Functionality: The updated Excel file can be re-imported to upload and update execution results and related details for test cases/step runs within the respective test cycle. The background process section will provide testers with any errors or warnings detected during the upload due to invalid or incorrect data. Audit logs will also record operations related to exporting and importing test cycles. Archive Enhancements
Archive test cycles and test plans before deletion to prevent accidental data loss. Testers must archive test cycles or test plans before deleting them. Users with edit permissions can archive or unarchive them. Testers cannot modify the details of archived test cycles, their executions, or test plans. Testers can't import test executions for the archived test cycles and their executions. The archived test cycles or plans are not displayed on their list views and will be accessible through a dedicated view. Archived test cycles and their associated executions will appear with a grey background in the link section of the story, test plan or test case. Testers can generate reports to include or exclude archived test cycles and plans. Archived test cycles are tagged separately in the traceability report. Security Enhancements Users now have the option to mask sensitive information, such as API keys and authorization tokens, in header values or the webhook body when creating or editing a CI/CD rule. These masked values will remain hidden in the user interface and cannot be retrieved, providing an added layer of protection for sensitive data. The audit logs will not display the old and the new values in the rule history. Jira administrators can now control access to modify QTM4J project settings by assigning permissions to specific Jira groups. By default, users with Jira's Project Administrator and Browse Project permissions will continue to have access. These configurations are under the QTM4J Global Settings > General Configuration. Bug Fixes Fixed a bug that prevented users from navigating to another test case through its URL inserted via the "Insert Link" option in the text editor within another test case. Fixed a bug that prevented uploading the JUnit test result automation file when the test case name attribute contained only numeric characters. Fixed a bug that prevented background colors from displaying for the test case, test cycle, and test plan workflow statuses in the Asset Macro table on Confluence pages. Fixed a bug that prevented error messages and failure logs from displaying for test case executions for JUnit and TestNG automation file imports uploaded via Automation Hierarchy 2 and 3. Fixed a bug that prevented displaying the correct latest test case execution result in the test case/acceptance criteria on the Story page.