Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
QMetry Test Management for Jira Server/Data Center v4.2.0
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.
Previous Versions
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 share reports with other users using a URL.
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.
Export all test cases of a folder directly from its context menu.
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.