Follow

QMetry 6.10 (6.10.06.09) - 29-July-2016

QMetry 6.10

Build 6.10.06.09 Released for OnPrem : July 30, 2016  &  SaaS : July 30, 2016

Introduction

InfoStretch is proud to announce version 6.10 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

Improved how users view and add test case versions in a cycle.

Updated UX so that when users view a test case details they see the version that is associated with the cycle rather than just the latest version. And if a user adds a test case to a test suite the version associated with the cyle is added.

User Story :  A requirement has been created specifying functionality in v1 of a hardware product. A test case is created to cover that functionality. The requirement is then updated with new functionality for release v2 the hardware. The test case is also updated to match that new functionality. Some time later a bug is found in v1 of the product and a patch needs to be created. The patch is created and QA decides to test the patch using a regression suite from v1 of the product. They create a new test cycle for the patch in release v1 and copy test cases and test suites associated with v1 (possibly requirements too depending on their process). Obviously they want the requirements and test cases that are associated with v1 and not the latest version of requirements and test cases from v2 which no longer match the v1 hardware.
Added the QMetry Version and Scope details while creating support ticket from QMetry.

When users create a new support ticket from the Qmetry interface the version of QMetry and the details of what scope the user is in when reporting the issue will be included in the support ticket.

Allow selected version of a test case to be added to another Domain
Parent & Child: Make child test Case read only.

Moving forward Child test cases are read only to avoid conflicts between versions.  If a team wants to modify a child test case in the sub-domain they must get the owner of the child test case to modify it.  A child test case can be copied.  A copied child test case can then be edited.

Parent & Child: Disabled the feature 'Push to Parent'.

Now that the Child can not be edited independently from the Parent the current option which allows child to be pushed to parent has been turned off. There is still an option to push the parent version to the children.

Enhanced Audit Trail for Domain
User Story :  As a user, I should be able to view the audit trail for activities on Domain like Update, Delete. Activity can be viewed by creating a custom query in the Reports Module.
Enhanced Audit Trail for Release
User Story :  As a user, I should be able to view the audit trail for activities on Release like Update, Delete. Activity can be viewed by creating a custom query in the Reports Module.
Enhanced Audit Trail for Cycle
User Story :  As a user, I should be able to view the audit trail for activities on Cycle like Update, Delete. Activity can be viewed by creating a custom query in the Reports Module.
Enhanced Audit Trail for Build
User Story :  As a user, I should be able to view the audit trail for activities on Build like Update, Delete. Activity can be viewed by creating a custom query in the Reports Module.
Enhanced Audit Trail for Platform
User Story :  As a user, I should be able to view the audit trail for activities on Platform like Update, Delete. Activity can be viewed by creating a custom query in the Reports Module.
Improved use of a blank value as default for lookup list.

Enhanced the UX to remove default values for all fields (e.g. the Test Case Type will no longer add a value unless selected in the manage fields option).  As a user I want to update a field so that it should not have a "Default Value"

Add the ability to map fields between modules.

The mapping of fields had previously been limited to a few system fields, now all system defined fields (SDF) and User Defined Fields (UDF) can be mapped from one module to another.  You can also map Test Case fields within a module to improve the ability to copy a record.

Enhanced Audit Trail for Issue Module
User Story :  As a user, I should be able to view the audit trail for activities in the Issue Module like Create/Edit/Delete Issue; Link/Unlink Attachment; Link/Unlink Requirement Edit/Delete. Issue activity is part of the Admin queries in the Reports Module
Enhanced Audit Trail for Test Case Module
User Story :  As a user, I should be able to view the audit trail for activities in the Test Case  Module like Create/Edit/Delete Test Case;  Link/Unlink Attachment; Link/Unlink Requirement Edit/Delete. Test Case Module activity is part of the Admin queries in the Reports Module
Enhanced Audit Trail for Test Suite Module
User Story :  As a user, I should be able to view the audit trail for activities in the Test Suite  Module like Create/Edit/Delete Test Suite;  Link/Unlink Attachment; Link/Unlink Requirement Edit/Delete. Test Suite Module activity is part of the Admin queries in the Reports Module
Enhanced Audit Trail for Requirement Module
User Story :  As a user, I should be able to view the audit trail for activities in the Requirement Module like Create/Edit/Delete Requirement; Link/Unlink Attachment; Link/Unlink Requirement Edit/Delete. Requirement activity is part of the Admin queries in the Reports Module
Added a search in the Add to Scope Pop Up

The search box has been added to all Add To Scope dialogs to help users with many different domains, releases, and/or cycles find the scope they are looking to add assets to.

User Story :  As a user I want a search functionality while selecting a scope so that I do not have to search through the long list of the scopes.
Allow selected version of a test case to be added to another Domain
Added extra security for JIRA links to Qmetry

Links to QMetry from JIRA must be opened from JIRA.  They will not work for anyone not already logged into JIRA.

Moved SMTP Settings for Feedback to database
User Story :  As a QMetry admin I want smtp settings for application to come from database in stead of from properties file so that I do not need to change the settings every time I deploy the application on my server.
Moved Email Notification URL to database
User Story :  As a QMetry admin I want to get rid of changing my EmailNotificationURL so that I can safely deploy and use my application on On-Premise when I am not using out-of-the-box settings for this.
Add report to show all the test case executions assigned to the current user
User Story :  As a QA Manager Fred wants a report that shows all the test case executions assigned to the current user so that they can quickly see what executions they have to execute.
User Story :   As a QA Manager I want a report that shows all the test case executions assigned to all users so that they can quickly see who has what assignments and review the statuses.
Add Update Button on Requirement Edit on permission based.
User Story :  As a QMetry user I want to have ""Update"" button for Requirement on permission based so that user can change in requirement fields by Update instead of creating a new version.
Add the ability to track Test Cases in the Activity Section of the Test Suite module.

Add the ability to track the  adding, removing, linking, and unlinking of Test Cases in the Activity Section of the Test Suite module.

Add the ability to track platforms in the Activity Section of the Test Suite module.

Add the ability to track the  adding, removing, linking, and unlinking of Platforms in the Activity Section of the Test Suite module.

Add the ability to track attachments in the Activity Section of the Test Suite module.

Add the ability to track the  adding, removing, linking, and unlinking of attachments in the Activity Section of the Test Suite module.

Add the ability to show or hide empty folders in the tree.
User Story :  As a user I want an option to show/hide empty folders in the tree so that I can easily search my assets without bumping into empty folders.
Allow the mapping of fields for Testcase to Test Case Mapping
User Story :  As an admin I would like to map  all System defined fields (SDF) or User Defined Fields (UDF) with other SDF/UDF based on my requirement so that I can copy values of one field to another while creating a copy of the testcase.
Implemented Background Exports in Reports
User Story :  As a QMetry Engineer I want to move export of the report to the background as we are having in Assets export so that we can continue working on other features while export is going on and we can remove the limitation of 3k records on export.
Provided Search in Scope
User Story :  As a user I want a search functionality while selecting a scope so that I do not have to search through the long list of the scopes. Considering a case when we have 100+ Domains and multiple releases and cycles within.
Fixed integration issue with FogBugz
Improved Select Scope Interface

Select Scope Interface now opens with all of the domains closed except for the current scope.  This speeds up load time and improves navigation.  Search was also added to help with large numbers of scope.

Added Customized Password Reset message for LDAP

Admins can not customize the reset message for LDAP users to provide the email for the appropriate IT person that can help reset the LDAP password.

Allow users to search internal issue tracker when linking issues to an execution

This matches the ability to search external tracker, but allows users that create issues in QMetry to also search and link those issues to an execution.

Parent & Child: Show Sync Status Column in Test Case Grid
User Story :  As a user of a child domain I want to be able to see if the child test case I am working on is the latest version, so I can know if there are modifications I may need.
Parent & Child: User can select to update status to 'Not Run' when using 'Push Latest Version to Child'

This option allows the version to be updated, but the existing test results to be preserved.

Parent & Child: Display Sync status next to version icon.

A sync icon will be displayed next to the version icon to show if the test case is out of sync (red= not in sync and green = in sync)

Improved automation integration by allowing it to wrok with a proxy server
Parent & Child: Export and Re-import of Parent and Child Test Cases

Allows the export and re-import of parent and child test cases.  Since child test cases can not be edited they will be ignored on re-import; however, any editable test cases that are being imported will be updated.

Added option to turn off audit trail logging

As a user I can able to on or off audit trail logging for: Test cases; Requirements; Test suites; and Issues

Parent & Child: Reset indicator based on "Approved" Status

This is developed for the Parent & Child QMetry Add on.  This feature makes it so that when a new version on parent is created QMetry would take a call if the version is final or draft based on Testcase State.  If the State is "Approved" then the Sync indicator will be reset  for the child.

Added notification when our instance is upgraded

When any maintenance is completed for customer then maintenance completion notification is sent to the customer. Maintenance Announcement in Login page should be disappeared without clearing cache at customer's instance.

Made Assign Tester notification so that it was user specific and not role based
Parent & Child: Sync attachments between parent and child

Attachment now sync between parent and child test case when we sync version across domains

Parent & Child: Force the push of a Parent to the Child when the Parent is Approved.
User Story :  I am user who is editing a Parent test case in my master library that I wants to automatically push the *approved* child test cases to my different vendors/teams in their child libraries so that they can start using them.
User Story :  I am user who is editing a Parent test case in my master library I wants to be able to _not_ automatically push *unapproved* child test cases so that my different vendors/teams are not confused by constant changes.
User Story :  I am user in the main library making changes to a Parent test case. The test case is in the draft mode and I want to get feedback from the vendor so I push (or pull) the draft test case to the vendor's domain so they can review and provide feedback. (note: the vendor can not pull the latest parent version since the vendor does not have rights to the parent domain).
User Story :  I am user in the child domain and I want to be able to determine if I have the latest version of the test case.
Added option to change the default reset status

Made it possible from the user profile to change the default selection when test case is edited / updated from Reset to do not reset by adding a "Reset Test Case Status to Not Run in current Cycle" option to user profile settings.

Improvements

Improved the display of domains in the user's profile.

The list of domains the user belongs to and the user's role in the domain can now be easily reviewed as a table.

Added My Testcase Execution Assignments to "Cycle" Dashboard
Added message when saving changes in SMTP settings window.
Fixed bug in reports that filtered records in a multi-lookup field incorrectly.

Reports will now properly filtered records in a multi-lookup field correctly, same as the main grids in other modules.

Fixed bug in cross domain report that returned archived domains.

Now on un-archived domains will be displayed when using cross-domain reports.

Enhanced grids in Admin Module to allow filters.

Filter option is now working for all fields in the following grids:
Notification Settings; Manage roles ; Nomenclature; Agent; and Execution status (Filter not available for all columns in execution status).

Enhanced report export to allow users to only export filtered data when exporting.
Improved tool tip for hover message over save.

Instead of "Save" tool tip now says "Enter all mandatory field(s) to enable the SAVE button"

Improved Tree View by refreshing tree after creating test suite folder
Improved performance of displaying test cases in cycles of some customers instances when there is a large number of tests
Improved Copy Test Case function to copy all fields and steps
User Story :   A tester is reviewing a test case and realizes that a second test scenario is possible with slightly different steps. The tester wants to copy the test case and make the changes
User Story :   An organization creates a series of templates. These templates have a set of common fields that are filled in, per-conditions, and steps (login, navigation, UI validations, etc.). The user copies the template and then completes the test case for the new test case.
User Story :   A tester has an ad hoc test that has minimal steps. The tester has used the test case in the early development stage and added a few pre-conditions and steps to improve the test case. Now the feature is 95% complete and the tester needs to create the final test cases. The tester wants to copy the ad hoc test and then complete it with the more detailed steps for 1 or more test cases.
Improved Copy Test Suite function to copy Test Runs

Bug Fixes

    • Fixed bug that didn't show details of first version in the Version History.The details of the first version would not show up until a second version was created.
    • Fixed bug that shows inactive users differently when users list was used for custom fields. Inactive users are now displayed the same in the user list no matter if the field is used for System Defined Fields (SDF) or User Defined Fields (UDF).
    • Fixed bug that sometimes showed  records before the provided date when search by Modified Date.
    • Fixed bug that shows different Statuses in Test suite section from Test Case detail window
    • Fixed bug that did not import Date values correctly to issue module.
    • Fixed bug with Fogbugz integration that prevented the component values to be imported correctly.
    • Fixed an incorrect error message provided when user exceeds the length of the JQL field in import.
    • Made additional improvements  to the revamped UI for QMetry issues linked to JIRA.When clicking on a QMetry Requirement or Test Case from JIRA a new User Interface is displayed with many improvements in both style and substance.
    • Improved the loading of the 'Test Case Execution Trend' report, "Domain summary" query and "login-logout" query.
    • Fixed bug that showed users in another domain had edited a test case.
    • Fixed bug in which Test Case search was not filtering data by modified date.
    • Fixed Domain Summary Report to properly show the correct data for attachments
    • Fixed bug in test case grid in which the attachments count was not refreshed when showing assets in the folder tree.
    • Fixed bug in which  a few special characters did not return proper search results.
    • Fixed bug that did not import test case owner when value was valid.
    • Corrected S Curve Report to show proper graph
    • Fixed bug in export to Excel for All testcases for Current Domain
    • Fixed bug in which a bulk edit of test cases with attachments accidently links the attachments to the rest of the test cases which were selected in bulk edit.
    • Fixed bug in which the button label did not display if the user chose to display only icons in their user profile.
    • Fixed a bug that prevented Admins from saving platforms with some combinations  of both "mandatory at run time" non-mandatory attributes without saved values.
    • Fixed bug that did not show red star for some mandatory fields.
    • Fixed bug that did not maintain the step sequence when exporting test cases from Test Suite
    • Fixed bug that did not let Admin's remove default value from Custom lists of some system fields.
    • Fixed Version Management & Activity Screens in which "Modified Date/Updated Date" was used instead of "Date Created"
    • Parent & Child: Fixed bug in which status was reset even when the option to reset status was unchecked.Now the old versions will remain linked to any existing test suites along with the status.  If the test case is added to a new test suite the new version will be added to the test suite.
    • Improved LDAP and LDAP SSL integration.LDAP was only working with default port 389 and LDAP SSL with default port 636.  Now LDAP or LDAPs can work with any port.
    • Fixed bug in which status was reset even when the option to reset status was unchecked, while creating a new version of test case : Now the old versions will remain linked to any existing test suites along with the status.  If the test case is added to a new test suite the new version will be added to the test suite. For executing latest version of testcase in existing test suite the test case should be linked again and the older version should be unlinked.

API Changes

Download the QMetry 6 - REST API Document - v6.10

Here are the API's added/modified in the document.

  • Export query in pdf/excel.

 

If you wish to upgrade to latest release please write us at support@qmetry.zendesk.com mentioning your current version and QMetry Support should provide you the upgrade guide.

QMetry is a Test Management software uniquely designed to improve the efficiency of Quality Assurance teams, while empowering teams to support their quality objectives. QMetry enables testing teams to focus on testing activities while providing a zero maintenance platform. With its centralized repository, QMetry makes it easy for team members to gather, organize and share information for successfully meeting quality objectives.

All trademarks are the property of their respective owners.©2016 QMetry. All rights reserved. www.QMetry.com Phone: (408) 727-1101 Email: sales@QMetry.com

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk