Here is the official link to Release Note 7.0, below is a quick summary for the Release 7.0.
Improved Automation Integration
Added support in automation integration utility for multiple test suites
Importing multiple automated test scenarios will create separate test suites for each test scenario and new test cases for each method / action within the test scenarios. Methods used in multiple test scenarios will be created only once.
Added the ability to create and update test suites and test cases through API
User Stories : • I am an automation engineer and I want to import my automation scripts as test cases so I don't have to manually create the test cases. • I am an automation engineer and I want to import my regression test suites as test suites so I don't have to manually create the test cases and test suites. • I am an automation engineer and I want to import a test suites into QTM that is a mix of existing and new test cases so that I can reuse the test cases already in the system and add new ones as needed.
Improved JIRA Integration
Added New Test Suite View
When viewing a test case from JIRA the Test Suite is now a link which will open to show the complete Test Suite Run information. The Test Suite will show all test cases in the test suite along with their status and and bugs filed against them.
User Stories : • I am a developer and I want to see the full details of why an issue was reopened so that I can analyze if the steps to reproduce were correct. • I am a QA Manager and I want to see the full details of a test suite so that I can review the steps that led to a bug or reopening of an issue. • I am a Product Manager and I want to see the full details of a test suite related to a test case so that I can review not just the steps that validated a new feature, but the regression test cases that were tested in relation to the new feature.
Show JIRA bugs as Links
When viewing Test Cases from JIRA any bugs filed against a test run are now links to the JIRA bug.
User Story : I am a JIRA user reviewing a test case. I see a bug in one of the executions and I want to open it to see the details.
User Story : I am a JIRA user reviewing a test case and want to know what scope(s) the test case was executed in.
Improved Linked Issue Details to Reduce Duplicate Bugs
When a tester clicks on the Add Bug button from the execution screen of QTM the user is shown a list of issues already linked to the test case. In QTM 6.0 this information was limited. In QTM 7 we have added Issue Status, Scope, Build, platform attribute, and Linked Date information
User Story : I am a tester who has found a bug and I want to be able to see (and possibly filter by) the various information related to previously linked issues before adding a bug, so that I can find better find similar bugs and avoid creating a duplicate.
Improved Test Case Details For Bugs
When a bug is created from a QTM test case the information from the test run is copied to the description. In QTM 6.0 and below fields that were empty were also copied. In QTM 7 we remove any empty fields test case and test case step fields to avoid unnecessary noise and improve readability
User Stories : • I am a tester and I want the steps to reproduce to be copied in a format that is clear to development so that I don't have to do a lot of manual editing to ensure development understands the issue. • I am a developer and I want to be able to read the steps to reproduce without having to scroll through a lot of garbage data so that I can see what the expected vs actual results were so I can understand and fix the issue faster.
Improved Use of webhooks
Added webhooks for linked issues so that bugs linked to executions can be updated immediately and without any scheduled JIRA queries that might impact performance.
User Story : As a QTM user using JIRA as bug tracking, I want updates happening on JIRA to be reflected in QTM with minimal performance impact so that I can see the changes in QTM and JIRA server has low negative performance impact.
Added Quick Start GuideNew users will be greeted with a role based help guided that will show the main UI/UX features of QTM. The guide will show different features based on the role of the user. The Quick Start Guide is also added to the help menu in the top tool bar for existing users.
- Added role based getting started guide for first time users
- Added in context help for Requirements Module
- Added in context help for Test Suite Module
- Added in context help for Test Case Module
- Added link to help menu to bring up help guides for existing users
User Story : As a new user to QTM I want to see some basic information on the QTM UI so I can better get started using QTM.
Improved Ability to Copy Assets Between Scopes
Added the ability to add different versions of a Test Case to Scope.
Companies that are using multiple versions of a test case can now use different versions of a Test Case in different releases and cycles. If a user is viewing an older version of a test case they will be asked if they want to copy that version, the latest version, or to select another version. The default will be to scope the version the user is currently viewing. I am a tester that needs to test a patch to the previous release of software / hardware. The test case has changed in the latest version so I need to add the old version to the new patch test cycle.
Added the ability to add different versions of a requirement to Scope.
Companies that are using multiple versions of a test case can now use different versions of a requirement in different releases and cycles. If a user is viewing an older version of a test case they will be asked if they want to copy that version, the latest version, or to select another version. The default will be to scope the version the user is currently viewing.
User Story : I am a QA Manager that needs to test a product release for a specific customer. The customer has not updated a particular module so I need to use the old requirement for that test cycle.
Added Test Case Version to the Copy Test Suite to Scope feature
Added option to the Test Suite Copy to Scope feature to allow users to copy the Test Case Version associated with the Test Suite. Previously when copying a test suite from one scope to another the latest version of the test cases would be copied rather than the version of the test case associated with the test suite. This maderegression testing difficult for some QA organizations that use multiple versions of a test case. (Read More)
User Story : I am a tester responsible for testing new releases and validating the releases in the field, I need to be able to copy a test suite with old versions of test cases, so that I can properly validate patches to old releases.
Added Test Runs to the Copy Test Suite to Scope feature
Added option to the Test Suite Copy to Scope feature to allow users to copy the linked Test Runs associated with the Test Suite. Previously when copying a test suite from one scope to another the platforms could be copied, but not the test runs Note: Test Runs is a feature of the Enterprise Edition of QTM. (Read More).
Improved Email Notifications
- Added new options for users to turn off individual email notifications from QTM
- Added an email notification of assignment
User Stories : • As a user, I want to stop receiving email notifications when I am the designer/owner so that I don't receive too many emails that are not needed. • As a user of a specific role, I want to stop receiving specific email notifications for that role so that I don't receive too many emails that I consider spam.
Improved Audit Trail
Add activity reports for each module so users can track changes.
Activity that is tracked are: Assets created, deleted, updated, archived, imported, exported, or linked/unlinked; Release/Cycle Deleted or Archived.
Added asset based Activity View.
An audit tab showing all activity related to an asset was added to all modules. This tracks activity related to versioning as well as any activity that does not effect version control like linking assets.
Improved Platform Matrix ViewNote: The Platform Matrix View is an Add On for QTM.
Added Checkbox to the rows in Platform Matrix to select all the checkboxes of that row
Added ability to filter by Status in Platform Matrix
User Story : I am a tester, I have 100 testcases linked to a testsuite and few platforms, few of them have blocked status. I want to filter the testcases by blocked status so I can execute them again. But I can't do so as platform matrix doesn't have the filter option on platform columns.
Miscellaneous New Features
Added Test Case Execution with Defect Coverage Report
This report provides a list of the latest Test Case Executions along with the issue details. If any execution has a defect this report will list the details of that defect. If an execution has multiple defects than the issue will show up multiple times.
Add full bulk status update options to the Test Case View of test suite module.
This option is primarily to allow users to quickly mark test cases “”Not Run”” or “”Not applicable”” across all test runs regardless of test suite or test run.I am a QA manager and I want to filter for specific test cases across all test runs regardless of test suite or test run and then change the status to “”Not Run”” as needed to force testers to retest using the latest build of software.
Added created date to the versions history
In some cases a version created date and modified date are different. Now the Version history shows the created date.
Added an option at the top of the Link Test Case UI to Hide already linked Test Cases.
I am a tester, I have 100 testcases to be linked to a testsuite, but I don’t know if I have linked few of the testcases already or not. I need a pop-up which will indicate if I am going to link a same testcase again to the same testsuite. I don’t want to link same testcase twice to same testsuite.
Added the number of assets to be deleted in the confirmation message to the user.
While deleting test cases there is a confirmation message. This message now includes the number of assets that will be deleted.
Added a link to the test suite in the execution history of a test case.
User Stories : • As a QA Manager, I want to be able to click on a the suite link when reviewing the execution history so that I can review the full test suite / test scenario to see what else may have failed, what steps proceeded the test case, etc. • As a user, I want to be able to click on a test suite link when reviewing the execution history so that I can review the full test run to see which step failed and what the actual results were for each step along with any additional information on the test suite. • a tester, I want to be able to click on a test suite link to find a regression suite that I want to then copy to scope for the current cycle.
Added version comments to the version management screen.
Version comments were added to the version management screen to help users to better clarify the differences between versions.
Added a My Assignments Dashboard
Moved the various My Assignment dashlets to a new “My Assignments” dashboard to improve the visibility and access to these reports.
Implemented Daylight Savings Time (DST) throughout QTM.
In some grids the date and time would show up without accounting for DST.
Added “Executed At” column to the Execution Status section of JIRA Test Case View.
Made ” Executed At ” field visible by default in the JIRA Test Case View so user can identify on which Date and Time the Test case was executed.
Changed Default Tree setting to Show Status
Showing status in the tree allows users to quickly see the aggregate status of folders in the tree.
Added new logo to QTM 7
QMetry Test Management 7 has been rebranded with the new logos.
Enhanced Step section of the Test Case View from JIRA
Moved the Input Data Field to the right of the Step section and minimized the width to give the description and actual results more room and improve readability.
Enhanced activity section of Test Suites to track additional changes.
Activity section of a Test Suite should track additional changes such as: add/remove test cases; change in platform ownership; Test case order changed Platforms linked or unlinked; Platform owner is changed; Attachment linked or unlinked.
Improved Display of Test Case Step
Step Description and Summary (Step Name) fields should display if both fields have value and should not display if both fields are blank
- Fixed ‘System Exception Error’ when changing ‘Assign Tester’ to ‘Unassigned’ for already assigned Tester
- Removed “Cost per hour” column from Manage users screen.
- Fixed API bug in which ‘Get Testcase Run Id using Testsuite Run id’ API gives only 10 Test Cases in response, if limit parameter is not provided.
- Fixed bug in which Unlink Requirement Audit Trail is not displayed in Test Case Detail.
- Fixed bug in which LDAP did not work with Customized ports
- Improved Activity tab export so that it includes the last change made in test case.
- Fixed bug which resulted blank screen after login to QMetry, when release is created without a cycle using API.
- Fixed bug which prevented requirement to be updated, when all values of multi-lookup list are deselected.
- Fixed bug that did not refresh test case details after update, when “Close edit window after update” setting is off in user profile.
- Fixed bug that prevented export of all records from activity section.
- Fixed bug which enabled “Edit” button on child test case detail screen if open from Parent.
- Fixed bug that did not display hyperlink to the assets in notification if assets were updated from API.
- Fixed bug that displayed incorrect Tester Name in assign Test case notification email.
- Fixed bug that erases execution history of Testcase Steps from a Testsuite, when Test case is unlinked.
- Fixed bug that prevented export of Testcase steps in correct order, from execution screen.
- Fixed bug with the search’s paging function with in which the scope changed when user paged through the records.
Announcement for QTM Cloud Upgrade
Work was made in the background to help transition the QTM cloud instances to a more secure and scalable architecture. This move will will help better support our SLAs. By moving to the new architecture we will be able to take advantage of using many tools to boost our performance and at the same time ease on the maintenance.The evaluation instances have already migrated to the new architecture. There will be a separate announcement to existing users providing timeline for the upgrade of their instances.