What's New
QMetry Test Management for Jira Server/Data Center v4.8.0
Introduced the 'Target vs Actual Execution' gadget within the Test Execution reports, empowering QA teams to monitor the current execution progress and comprehend the existing and necessary execution rates to meet delivery timelines. Generate the report in one of three modes based on the testing process followed by project teams.
Target Completion Date
Execution Velocity
Execution Planned Dates
Project Administrators, i.e. users with QTM4J configuration modification rights, can now copy custom fields along with their list values within the following scopes:
Within the same project, i.e. from one module to another module
Across the different projects, i.e. from a module in the source project to selected modules in the destination project
Introduced date field 'Planned On' on the execution screen to enable testers to plan and track their assigned test executions on specific dates.
Grid View
List View
The Test Cycle's linked Test Case section displays test case custom fields along with the default system fields.
The Test Plan list view presents a consolidated execution summary of its associated test cycles.
The Test Plan's linked Test Cycle section displays test cycle custom fields along the default system fields.
Previous Versions
Start new test case executions individually or in bulk directly from the Test Case Acceptance Criteria panel on the Story page within an existing test cycle. Users can choose their preferred environment, build, and assignee while starting these executions.
Create an 'Ad Hoc' test cycle and perform executions for test cases directly from the Test Case Acceptance Criteria panel on the story page by specifying the desired environment, build, and assignee.
While executing the test cases from the story or the test case execution section, fill in the execution custom fields and the execution system fields, along with changing the execution status.
Import existing components from a Jira project into QTM4J components.
Introduced an option in the manage apps global settings that automatically consolidates all QMetry panels into a unified section, significantly enhancing the loading performance of the Jira Issue page.
Manage shareable test cases through a dedicated view within the test case module.
Create a shareable test case from an existing test case or independently from a dedicated new section. Additionally, shareable test cases can be versioned.
Insert shareable test cases as steps into another test case of the same or cross-project to reuse common steps.
Shareable test cases can include parameterized steps, and they will reference the parameter values from the test cases that reuse them.
Easily sync the latest version of the shared test case directly from within the associated test cases.
During test execution, the test case containing shareable steps displays the steps as usual, along with a reference to the shared test cases
Enable testers to conveniently copy test case steps from an existing test case while creating or modifying a test case, using the option "Copy steps from existing test case".
Copy and maintain the folder hierarchy of test cases when exporting them in bulk to other projects.
Search test cases within a project repository on specific keywords found within the description, pre-condition, and steps in addition to the summary.
Start New Execution in bulk for test cases on a selected environment.
The new 'Test Cycle Execution Summary' section on the Story page displays the test cycle details linked directly with the story and its execution summary, enabling better coverage and traceability.
Introduced the "Coverage by Test Cycle" report that displays the count and details of test cycles, both directly linked and not directly associated with the requirements.
Introduced the "Coverage by Requirement" report that displays the count and details of requirements, both directly linked and not directly linked to test cycles.
Improved collaboration and reusability - Report owners can share the filter criteria with other users by granting view and edit permissions.
The Test Cycle > Test Cases tab and the execution screen now indicate the availability of a newer version of a test case besides the older linked version.
The test case detail now includes a system Pre-Condition field and is visible on the execution screen above the step details.
Improvements to Test Case Import via Excel: Testers can now import test cases with parameterized steps using the Excel import feature.
Users can now bulk-create parameters and values by importing them using Excel from the configuration page.
Introduced a new "Steps to Reproduce" section on the bug page that auto-captures the test steps and test execution details, eliminating efforts by testers to add them manually.
Previous Versions
Introducing timeframe reports - Generate daily, weekly, monthly, and yearly test case and test execution summary reports to keep track of progress.
Drill down the graphical report charts to view and export the filtered records.
Generate test case summary report grouped by a custom field for a selected project.
Clone test cycles in other projects with the following options -
Clone test cycles as not executed or by retaining test case execution statuses.
Clone the latest or all executions of the test cases.
Clone test cycles with additional options for copying associated defects, attachments, comments, execution custom fields/values and actual results.
Bulk clone up to 20 test cycles in the same or another project.
Filter test case execution runs on all system and custom test case fields.
Filter unassigned test executions and bulk assign them to a tester.
Import Attachments
Upload attachments to test cases and steps while importing through excel by mapping attachment folders and names.
Attachment Enhancements
Inline Attachments: Add inline images to textboxes using the copy & paste, browse & upload, and drag & drop options; click to view them.
Attachment Section:
Introduced a new thumbnail (strip) view that displays the preview of attachments.
Copy & paste screenshots to upload them as attachments.
Click on the images and files under attachments to view them without downloading.
Copy the URL of an uploaded attachment and paste it as an inline image into a test asset.
Folder Structure Enhancements
Get a consolidated view of the test cases in the folder hierarchy by displaying test cases of subfolders in the parent folder. This setting can be enabled on the following screens and saved per the user's preference.
Test Case module - list screen.
Link test cases to the test cycle from its test case tab.
Link existing test cases to a story in the test case/acceptance criteria section.
Execution Screen Enhancements
Filter test case executions by the execution custom fields.
Perform bulk updates to the execution custom fields during test executions.
Perform clone of test cycles & test execution runs containing execution custom field values.
View and set execution custom field values while executing test cases directly from the story and the test case's execution tab.
Customization Enhancements
Make system and custom fields mandatory for test cases, test cycles, test executions and test plans based on the project workflow.
BDD Support and Integration with Version Control Repositories
Organizations practicing Behavior-Driven Development (BDD) can author a feature file using the built-in Gherkin editor in Jira story and sync it with Version Control Systems (VCS) like GitHub, GitLab, and Bitbucket on Cloud & Self-Hosted editions.
The developers, testers, and product owners can push or pull commits made to the feature file from within the story page to achieve two-way syncing between QTM4J & VCS repositories.
The QTM4J project settings have the configurations for integrating the VCS repository for a project. A project can have multiple VCS repositories integrated with it.
Automated test cases get created/reused based on the feature step definitions. The test cycle stores the automation execution results and displays complete feature traceability with stories.
QTM4J Confluence Integration (Only for Data Center hosting)
Introducing a new "QTM4J Confluence Integration" app for Jira data center hosting with the following features:
Embed a widget that dynamically displays filtered QMetry test assets in a tabular view containing the fields selected by the users.
Display a single test asset with a hyperlink while mentioning it on the page.
Create a test asset in QTM4J and display its reference on your page without leaving the Confluence editor.
Custom Fields to capture execution details
Create custom fields for test execution to capture additional details specific to a test case execution runs:
Administrators can create custom fields for test execution from project configuration settings.
View the custom fields on the execution screen while executing the test cases.
Export of the test execution records from the execution screen will include execution custom fields.
Export of the test case execution summary and traceability reports will contain execution custom fields.
Book Demo or Chat with QTM4J expert
Users can book a demo or chat with a QTM4J expert by selecting an option from the QTM4J menu bar.
Link Jira stories with the test cases during import through Excel by defining story keys. Jira stories linked to the test cases will also be available in the exported excel.
The total count of test assets in the folder hierarchy is now displayed next to the folder name, along with the count of test assets in the folder.
The project administrator can configure the default grouping and sorting of test cases displayed on the execution screen grid view for all the users.
Bulk clone up to 100 test cases with the latest version, attachment, and comment in the same project.
Public filters can be shared with other users using a URL.
The Test cycle view in a Test Plan now displays an Execution Summary(tabular) column to show the count of test case execution based on status.
Test case execution reports are now available in Pie and Line charts.
Status and Priority field values can now be archived if not required for the workflow.
Introduced new Test Case Summary reports grouped by: Assignee, Reporter, Sprint, Fix version.
Improvements to Traceability report:
Option to generate the report only for the latest execution or all executions for a test case.
Traceability report export now includes test plan details.
Filter all the reports based on custom fields associated with test cases, test cycles, and test plans.
All Test Case and Test Execution reports provide an option to export data with or without steps.
Jira administrators can set default pagination for all the users from QTM4J Global Settings.
Users can override the pagination default value for their profile from the project configuration > general settings.
Project Administrators can set default columns visible to all users on the module list views from QTM4J settings for their project.
Now view/add/modify/clone/delete test case steps directly from the story page.
Execute test cases that are linked to the test cycle from the execution tab, on the story page, instead of navigating to the execution screen.
Create a test cycle directly from the story, with all the test cases associated with the story auto-linked to the test cycle.
Link selective test cases associated with the story to an existing test cycle.
Link multiple versions of a test case to the story to get accurate end-to-end traceability.
Now view/add/modify/delete/clone test case steps from the test case list view.
Execute test cases linked to the test cycle directly from the Test Execution tab, instead of navigating to the execution screen.
Import test cases from excel to multiple folders by mapping folder path during import.
View the entire content of test steps using the expand/collapse quick buttons available at the step grid.
Update the test cycle/test plan summary directly from the list view.
Save filters applied to columns on test cycle/test plan as public or private.
Redesigned the "clone" test cycle screen with an additional test case filter on the execution assignee.
View/add/modify/delete/clone test case steps directly from the Test Cycle > Test Case tab.
Added Execution Summary(tabular) column on Test Cycle List view to show the count of test case execution based on status.
All-New Test Execution Screen - List View.
Improvements to Existing Test Execution Screen – Grid View.
Revamped Test Execution Grid View now has two tabs - Test case details & Execution.
The execution tab now has 4 sections that can be re-ordered – Steps, Bugs, Attachments, and Comments.
Attachments uploaded while authoring test cases/steps are now available on the execution screen.