Manager 10.0.1 Release Notes

April 8, 2020

We are happy to announce the release of qTest Manager 10.0.1 SaaS. This release includes exciting enhancements to qTest/Tosca integration, as well as improved performance for the Tree Navigation for Requirements, Test design, and the Test Execution tabs. There are new features for the Admin User Groups and several Security Enhancements.

Review the End of Support Announcements for qTest for important information on upcoming API changes and additional deprecations.

Tosca integration improvements

Hyperlink from Tosca to qTest

A hyperlink is now available from each Tosca Test Case to view in qTest. You can right click on the Tosca Test Case and click View in Test Case. For more information on this update from Tosca, refer to the Tricentis Tosca documentation.

Tosca nested folder structure

The entire folder structure of a Tosca Test Case can be exported into qTest.

  1. Select all folders that you would like to send to qTest from Tosca.

  2. Right click the folders and click Create/Update in qTest.

  3. All folders will be in qTest immediately.

Admin user group changes

Administrators can now add Projects to their User Groups so that users can be automatically assigned to a Project when they are added to User Groups.

Administrators can automatically assign users to Projects when adding users to User Groups.

Cut, copy, and paste from grid for Requirements, Test Design, and Test Execution tabs

There are new updates to the Requirements, Test Design, and Test Execution Tabs for users with the appropriate permissions. Users can cut or copy Requirements, Test Runs or Test Cases from a grid to another folder using context menu. All of the properties are included within the items pasted.

Permissions required

  • Requirements:

    • Copy requires Create Requirement permission.

    • Cut requires Edit Requirement permission.

  • Test Design:

    • Copy requires Create Test Case permission.

    • Cut requires Edit Test Case permission.

  • Test Execution:

    • Copy requires Create Test Run permission.

    • Cut requires Edit Test Run permission.

Copy, cut, and paste from grid for Test Execution

  1. Select the Test Execution tab.

  2. Open any Release, Suite, or Cycle to view all of the Test Runs in the main container.

  3. In the main container, look for the list of all Test Runs that pertain to the folder selected and select all Test Runs that need to be moved to a different folder. You can select multiple.

  4. Right click any of the Test Runs that need to be moved.

    • Select Cut to remove the Test Runs from this folder to be pasted in the new folder.

    • Select Copy to keep a copy of the Test Runs in this folder and have a copy to be pasted in the new folder.

  5. From the tree panel, right click the folder you wish to move the Test Runs to and select Paste.

  6. The selected Test Runs are copied to the new folder.

Copy, cut, and paste from grid for Requirements and Test Design

  1. Select the Requirements or Test Design tab.

  2. Select any Module to view all Requirements/Test Cases in the main container.

  3. In the main container, look for the list of all Requirements/Test Cases that pertain to the folder selected and select all that need to be moved to a different folder. You can select multiple.

  4. Right click any of the Requirements/Test Cases that need to be moved.

    • Select Cut to remove the Requirements/Test Cases from this folder to be pasted in the new folder.

    • Select Copy to keep a copy of the Requirements/Test Cases in this folder and have a copy to be pasted in the new folder.

  5. From the tree panel, right click the folder you wish to move the Requirements/Test Cases to and select Paste.

  6. The selected Requirements/Test Cases are copied to the new folder.

Test Run grid performance improvements

The Test Execution page now has enhanced performance when loading the Test Run grid. Additionally, the Logs column has been removed from the default Test Runs grid view for Release, Test Cycle and Test Suite.

Jira rate limiting reminder

Beginning with Jira 8.6, Atlassian introduced rate limiting for Jira Server/Data Center. Customers can limit the number of calls Jira can make and receive. This setting is enabled in your Jira instance by your Jira Administrator. If rate limiting is enabled, it may delay updates between qTest and Jira. For more information about this change, refer to this article from Atlassian.

In response to this change, qTest has added the following modifications when rate limiting is turned on in your Jira instance:

  • When the Jira connection is being rate limited, users will receive message banners advising them of the wait time until they can try their action again.

  • When one task in the queue to a Jira connection gets rate limited, all of the tasks in the queue to the same Jira connection, will be delayed until the "try after" time is complete.

  • qTest APIs for Jira integration will return a 429 code when qTest is rate limited.

Users will be informed of qTest being rate limited when:

  • Jira Requirement/Release is out of sync

  • Create/edit a Jira connection

  • Retrieve Defects in Add Test Runs dialog > Defect tab

  • Link Defects in Test Execution History

  • Submit a new Defect and link it to a Test Log or a Test Step Log (includes QuickRun, TestPad)

  • Link an existing Defect to a Test Log or a Test Step Log (includes QuickRun, TestPad)

  • Manually retrieve data of a Requirement or a Release

  • Configuring a connection to Jira

Example error message: "The action cannot be done at the moment due to the rate limiting configuration of your Jira administrator. Please try again after ... If this issue is becoming more frequent, please contact your Jira administrator to change the configuration accordingly."

Security enhancements

  • In our continued effort to protect user data, we have implemented several changes. URLs in the Product Navigator will no longer have the username displayed when moving between apps. The user password will no longer remain in DOM after hitting submit.

  • The comments section on several tabs now has filtering for special characters, blocking execution of XSS that can be used to hijack information.

Bug fixes

Ticket # Component

Description
33090 Test Execution Depending on the time of the day, users report a page load that exceeds 1 minute for the Test Execution page. This has been fixed.
36624 Test Execution When some users were exporting the test runs with "Automation Test Runs" option, nothing would occur. This has been resolved.
36336 Test Execution In Firefox, when users clicked to create a Test Step, a Carriage return was added before typing began. This has been fixed.
37537 Test Design While loading data in Test Design Tab, users are facing slowness and continual buffering. This has been resolved.
31698 Test Case The file name is broken when downloading attachments with Korean file names. This has been fixed.
28885 Notification Emails Users were experiencing errors when copying and pasting the event template for notifications. This has been fixed.
N/A N/A Java SDK 1.4.9 and Katalon have been removed from the Resources page.