QMetry 6.8 (

QMetry 6.8

Build Released for OnPrem : May 6, 2016  &  SaaS : 15th May

Release Notes Link


InfoStretch is proud to announce version 6.8 which comes with fantastic new features, a lot of enhancements, and some bug fixes for all QMetry users.

If you are a QMetry 5 user and you want to understand the major difference between the two version please read our What’s New in QMetry 6 page.

New Features

Added options to open asset details in maximized mode to improve usability

Added 3 options in Admin>Profile>User Interface Settings to automatically maximize windows:

  1. Maximize module window
  2. Maximize asset window
  3. Maximize steps in Test Case window
  4. Maximize steps in Test Case window On Edit
User Story :  I am a tester and I want test cases to open with the steps maximized because the steps are the most important part of the test case and most of my test cases have a large number of steps.
Added "Fix Version" field to be displayed for both Requirements and Issue module

The "Fix Version" field was not available to be added to views and now it is.

Added the ability to Archive custom list values.

Users with the appropriate permissions can now archive individual values of a custom list.  The list value will not be deleted and will still remain in the history of assets that have used them.  Any asset that is currently assigned the value will remained assigned to the value until a user changes it.  Archived values will have "[X]" next to the value to indicate that it is archived.

Added the ability to view User Defined Fields (UDFs) to the Execution Screen

Both Test Case and Test Case Step UDF fields are not visible on the execution screen.

Show Version information in the Test Case and Requirement Details

Now instead of just seeing the version number of an asset users are able to see:
Version Number
Version Name (if there is one)
User who modified asset (e.g. Created version)
Date of the modified  asset (when version was created)

User Story :  A user is reviewing a common test case that has multiple versions that are applicable in different scenarios.  There are too many test cases to remember which version of each test case is relevant for the different scenarios so this extra information helps to select the correct test case version.
Added support for showing Test Case step custom fields on Execution Screen.

Users can now view Test Case step UDFs on Execution Screen.

Added Filters to the S-curve report

Added a new Filter menu to the S-curve report.  This allows users to fitler the S-Curve report by selected test suite(s).

Added the ability to Archive Platform Groups

Added the ability to archive platform groups in QMetry Enterprise to enable organizations with large numbers of platform groups to quickly archive large groups of platforms that are no longer needed for testing.

Added the ability to create and save views to Execution Screen

This is the same feature that is available in the modules' grid view that allows users to add, remove and move columns to the grid and then save that custom view so it can be used repeatedly.
The Execution Screen View saves changes to both the test case and test case step columns.

Added an option in the user profile to allow users to choose to wrap the summary field.

To avoid tall rows the summary does not wrap by default when the column is not wide enough.  Now there is an option in the user profile to allow users to choose to wrap the summary field.

Enable FixVersion system defined field to be viewed on Issue Grid
Added an option to Re-Enter external issue tracker credentials on a user's profile

This feature was added to handle cases in which the user's credentials had changed, or they had input the wrong credentials in the past.

Added 'Testcase Folder Path' to the 'Testcase Execution Status' report
Added Audit trails for all entity types and modules

Added Audit trails for all entity types and modules: Test Suite, Admin, Test Case, Requirement, and Issue.
Previously Qmetry tracked the changes, but didn’t provide an easy method for admins to view the log.

Updated Export UX to run in background as a scheduled job.

Export was moved to be a background activity to reduce CPU consumption and better support large exports of data.  Now instead of exporting everything at once we export 200 rows of data at a time. This change frees up the memory much more frequently, keeping Java’s garbage collector free, which was the cause of CPU consumption with the bulk export.
This new methodology supports more than  100,000 records exported in around 30 minutes, with no significant impact to CPU usage allowing normal use of QMetry from all users during export.

Implement Web Agent Configuration Screen

A JSON Automation Web Agent (JAWA) allows an automation engineer to define multiple web agents with different JSON variables. These JAWAs can then be used by manual testers to run automation tests with different values for the various variables.

User Story :   An organization needs to design automation tests that need to be manually kicked off.  The automation tests have multiple variable that change at runtime that they need the manual tester to enter. There are many different variables, but not all automation tests need each variable.
Added ID column in Reports module

Users can now better identify and sort reports by ID column.
This also helps find the reports that correspond to the dashlets in Dashboard since all reports are identified by ID.

Added "Not Run" and other status levels as option for the Platform Matrix UI

The  Platform Matrix is an Enterprise feature.  Previously users could change the status of test cases in bulk to "Not Applicable" only.  Now users can choose any status level.

On-Premise/Installed Editions : Move from Glassfish to Payara Application server.
User Story : Payara is derived from Glassfish and also provides the commercial support, whereas commercial support for Glassfish was ended by Oracle. Payara is on version 4.1 where before we were on version 4.0. This brings us to the latest version.


Improved the ability to assign users in the Platform Matrix View

For Enterprise users the Platform Matrix View is available and has been improved with the new drop down list to help large enterprises find the testers that need to be assigned- no more long scrolling list of users!
Also added was an option to remove an assignment and leave the test case unassigned.

Improved the importing feature so that all assets are created in the same order as they are found in the source file.
User Story :  A user creates a series of test cases in a logical order to be tested, one after another- and after creating those test cases the users wants to import the excel file with the test cases in the same order as they are found in the excel file allowing them to be easily added to a test suite in the same order.
User Story :  A user creates a series of test cases in a logical order to be tested, one after another- and after creating those test cases the users wants to import the excel file to a specific folder with the test cases in the same order as they are found in the excel file allowing them to be sorted in the folder by creation date / order.
Added support for showing the Test Case ID on Execution Screen.

Users can now show the test case ID as well as  export from execution screen.

Improved content of email body and signature

Added proper variables to email body and signature.

Improved Firefox Browser performance in which a Stop Script error was reported upon opening Reports with pagination limit greater than 100

It is still recommended not to have large pagination due to inherint browser limitations.

Updated Link Platform Window

Changed column name from "Summary" to "Platform" and removed the search UI since it searched for test suites was confusing.

Improved UX to guide users on which fields are mandatory when creating a test case
Improved email notification to suport portal for user who raise support tickets using QMetry Feedback (Bug-Feedback) options on main toolbar

Bug Fixes

  • Fixed bug to improve the reseting of the default values of reports when users clicks “Reset All” button
  • Export of bulk test cases may cause QMetry to go down.
  • Fixed bug that created System Exceptions on Execution screen if Attribute column is longer than 255 characters.
  • Fixed integration with cloud JIRA based on unannounced version change.
  • Fixed bug in which the focus on the comments box on the test suite execution screen was wrong.
  • Fixed bug that failed to show linked Test Cases does in the Test Suite detail screen if the layout is set in the Expanded form by default.
  • Fixed bug in which password reset emails were not being sent.
  • Fixed bug that did not preserve Test Case order  in test suite  while creating a schedule JSON
  • Fixed bug in which user can not properly log out of QMetry  when logged into multiple browsers, or logged out by admin.
  • Fixed bug in which the manage custom field showed the wrong associated modules for fields.
  • Fixed UI issue in which the Version History of a test case would include steps that had not changed along with those that had changed.
  • Fixed bug in which the link sent from a Qmetry share will not open properly in browser when user is not logged in.
  • Fixed bug in which search export will export all data regardless of search result.
  • Fixed bug that prevented Reset Password to be sent for servers using "https".
  • Fix version values are now Imported in Issue and Requirement module
  • Filter on Multi Look Up List is not working for test case and test case step
  • Fixed integration bug with Fogbugz v8.8.55.0
  • Children section in test case detail not displays records if by default that section is in expanded mode from layout management
  • Fixed bug in which Dashboard name was missing from left panel if the dashboard is opened from Reports module
  • Removed 'Read more' link in description field when there is nothing more to read.

 API Changes

Download the QMetry 6.8 - REST API Document. Here are the new API's added in the document.

  • Get Testcases Step
  • Update Testcases
  • Deactivate User
  • Delete User
  • Create Build
  • Create Release
  • Create Cycle
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk