Menu

Manager 9.2.1+ OnDemand Release Notes

Manager 9.2.7-1 October 26, 2018

Bug Fixes

  • Tickets 21783, 21708: Previously, the 'auto-test-logs'API endpoint failed to create Test Runs correctly. This has been resolved. 

Manager 9.2.7 October 22, 2018

Bug Fixes and Improvements

  • Ticket 17832: Users can use Korean in Profile Details. Previously, users could not add Korean in the "Field name" section of My Profile.
  • Ticket 16994: If users add a Test Step in between existing steps, tabbing no longer skips the newly added step. Previously, tabbing skipped this new step.
  • Ticket 20644: Users can now query by requirements with Target Release/Build by "N/A." 
  • Ticket 21559: Previously, changing the status of a test case and saving fails to update the test case. "Saving failed. Please try again later" message would appear. This has been resolved.

Manager 9.2.6 October 9, 2018

This release enhances the performance of the US-E production environment.

Manager 9.2.5 October 2, 2018

Bug Fixes

  • Ticket 17232: Previously, in Test Design when a user would tab from a step description to the expected result description, they could not type into the field as the rich text editor closes. This has been resolved.
  • Ticket 18166: When exporting a data query to excel, a title of 'null' was given to the excel file when a data query name was not provided. This has been resolved.
  • Ticket 18830: Previously, when using the API the PUT request would have missing values in the rich text field, of a Requirement and Release object. This has been fixed. 

Manager 9.2.4 September 26, 2018

Enhancements

Addition of Flood to the 9-Box

We are happy to announce that Flood is now a feature in your qTest suite 9-box. 
Flood is a cloud-based load testing tool that gives users the flexibility to test with millions of concurrent users in just minutes, using a shared cloud or your own private cloud resources.
The results from these tests are aggregated into a real-time dashboard so you can investigate and pinpoint the root cause of performance problems as they occur.
 
With an open REST API, it is easy to launch performance tests from any scheduling service like qTest Launch, Jenkins, or Bamboo so that performance testing can happen within your CI/CD pipeline. 
 
Note: Flood is currently only available in the 9-box for OnDemand versions. This new feature will be available for OnPremise customers in a future release.
 
Note: Flood can be accessed by any qTest user regardless of permission and qTest edition.
 
You can execute the following test frameworks within Flood:
  • JMeter
  • Gatling 
  • Flood Element
  • Selenium 
  • Tosca
As an exclusive for QASymphony customers, you are granted 20 node hours which allows you to run a 1-hour test with up to 20,000 users.
 
Read here for more information on how to get started with Flood, or reach out to your customer success manager/sales representative for a quick start session.
 

Accessing Flood

Accessing Flood from your qTest suite is easy. To do so, follow these steps:

      1. Select the 9-box, and choose the Flood icon from the 9-box menu.
      2. You are redirected to the Flood suite. Take note:
        • New Flood users will have a fresh account
        • Existing Flood users' accounts will be linked, and they will be taken to their already existing Flood accounts.
        • Projects will automatically be created within Flood to mirror what users already have in qTest.
          • Note: There is an option to disconnect your qTest projects from your Flood account. To do so, select the Integration option in your user drop-down menu.
            disconnet_qTest.png
            • The "Integrations" page displays. Here, you can see your qTest projects associated with your Flood account. To disconnect, select the Disconnect icon.
              Disconnect_option.png

Bug Fixes and Improvements

      • Ticket 20264: Cucumber results from Jenkins builds now successfully send to qTest. Previously, if a child folder existed under a module containing the cucumber features, those results would fail to send from Jenkins to qTest.
      • Ticket 19644: Data concerning the percentage of passed tests are consistent between the Test Execution summary and the Statistics tab. Previously, values were rounded in the Test Execution summary but truncated in the Statistics tab.
      • Ticket 18518: When retrieving requirements using the Gets multiple requirements endpoint, qTest no longer produces incorrect results. Previously, both duplicate requirements were populated, and some requirements were missing.

Known Limitations

If you had submitted test logs from a Jenkins Project to qTest before, you should pay attention to avoid setting the "Parent Module" (in Automation Settings > CI Tool) to be one of the descendant modules (if any) of qTest's Automation Module (automatically created by Jenkins on the first build). Otherwise, that will cause an infinite loop, causing the Web UI to crash. We are working to prevent that from happening in a future hotfix.

Manager 9.2.3 September 20, 2018

Improvements

      • Tickets 18352, 18639, 18018: Previously, the SAML Token expired after eight hours which caused customers who signed on via SSO to have trouble logging in without routinely clearing their cache. 
        The timeout configuration has been extended from eight hours to one week. This allows customers who need longer log-in sessions to login via SSO without routinely clearing their cache information. 

Bug Fix

      • Ticket 18755: Users can now successfully email Test Run Summary by Assignees reports. Previously, this feature was not working properly. 

Manager 9.2.2 September 11, 2018

Improvement

Jira Release Integration in Sync with qTest

The Jira Release Integration allows you to select which Release/Fix Versions or Sprints to sync with qTest with a status of "Unreleased". When a Fix Version was updated to "Released" in Jira, qTest would no longer update with the new "Released" status. This meant that the corresponding Release in qTest shows as "Unreleased" when in reality it is "Released" in Jira. 

This feature has been improved and will now display the correct Jira Status in qTest if you have configured your Jira Release Integration to retrieve only Unreleased Versions. 

      • If a Jira Release or Sprint has already been synced with qTest, it will update accordingly when an Unreleased Version is updated to Released.
      • If a Jira Release or Sprint has a Fix Version of Unreleased and it has not been previously synced to qTest, it will sync to qTest.
      • If a Jira Release or Sprint has a Fix Version of Released and it has not been previously synced to qTest, it will not sync to qTest.

Bug Fixes

      • Tickets 17738, 16061: You will now receive one password reset reminder email per day when it is close to your password expiration deadline.  Previously, some users were receiving multiple emails per day. This is resolved. 
      • Ticket 19057: Previously, when importing requirements via JIRA integration, that included a special character would display as HTML code in the folder name. This is fixed.
      • Ticket 18636: In the Test Suite view, column sorting did not work properly and would provide a 500 error when ID was not the first column in the grid. This has been resolved.
      • Ticket 17164: You can now use drag and drop to reorder Site Fields while in Site Administration. This is fixed. 

Manager 9.2.1 August 30, 2018

New Features

Search for JIRA Defects in Test Execution and the TestPad

You can now search JIRA Defects by free text as long as the 'Also populate JIRA defects that are not linked to Manager Test Runs' option is enabled in your JIRA Integration settings. This new feature is available in the TestPad and Test Execution grid.

testpad_defect_search.png

The defects that return will match the search material, along with their issue types that you configure in your integration settings.

The search results grid provides you with:

      • Defect Name and Description 
      • Defect Status

Select the checkbox for the desired defect and Add. This adds the resulting defects to a Test Log.

testpad_defect_search_results.png

Requirements Synced with JIRA 

Custom Fields for JIRA Requirements that sync to qTest displays the "Content Change" hyperlink in the History tab.  Previously, the JIRA API would return a long JSON string. 

Bug Fixes and Improvements

      • Ticket 15954: Hyperlinks in the Rich Text Editor now opens when you click on the URL.  Previously, to open the URL you would need to also select the Shift key. This has been fixed.
      • Ticket 15998: Multiple Selection fields will now show the first two selections followed by the total number of selections in parentheses. Multiple Selection combo boxes will show the total number of selections in the display field. 
      • Ticket 16835: The scroll bar on a TestPad is now displaying properly. This is resolved.
      • Ticket 17337, 19325: Previously, if a user had an apostrophe in their username the TestPad would be in a constant loading pattern when trying to open in a new window. This has been fixed.
      • Ticket 18612: Releases were not being created if 'link to requirements' checkbox is selected. This is resolved.
      • Ticket 17902: You will now see all of your unlinked JIRA Defects in Insights. 

 

Powered by Zendesk