Manager 9.4 OnDemand Release Notes December 20, 2018


We are pleased to announce the release of Manager 9.4. Listed below are just a few of the following improvements and enhancements:

  • several Jira issue page improvements
  • ability to configure stricter passwords
  • custom data queries are now visible when creating a test run
  • updated Manage Project Settings permission
  • many more!

Jira Issue Page Improvements


New qTest:Test Execution Icon in Jira Issue

The qTest:Test Execution add-on is now easily visible by the addition of a new icon, which is now located to the right of the attachments icon.


Filter Test Execution Data in Jira using Test Run Fields

This improvement includes a filter and summary in the qTest:Test Execution iframe that is visible in your Jira Issue. This is beneficial for situations when a Jira issue (User Story) is linked to a Test Case that is executed many times, which results in multiple Test Runs, such as with a Regression Test.

Additionally, you can select multiple filters as well as multiple values for each filter ex: Release filter, you can select Release 1, Release 2, and Release 3.
Please note, that your filters will not save. Therefore, whenever the page is reloaded the filters are removed and reset to display “All” as the default.

The new filters available for the Test Run level include:

  • Project
  • Release
  • Test Cycle
  • Test Suite
  • Status

Once the filters are updated, each Test Case will display the 5 most recent Test Runs, ordered by the latest Test Log’s Executed End Date.
If there are no Test Runs that match your selected filter(s), you will still see the Test Cases displayed, but will receive a message of “No Test Runs match your filter.”


Statistics Summary Bar Chart Now Available in Jira for Linked Test Runs

 A bar chart has been added to the qTest: Test Execution iframe in Jira that displays the total number of all related Test Runs for a Test Case. The bar chart is a statistics summary that groups your Test Runs by Status and includes any custom Status(es) that are set by a user.

Please note, that this bar chart is a total count of Test Runs by Test Case, however, the Test Case displayed will only show the last 5 executed Test Runs in the Jira issue. To view all the Test Runs that are associated with the Test Case, and accounted for in the statistics summary, you will need to navigate back to qTest Manager.
The available statuses are:

  • Failed
  • Incomplete
  • Blocked
  • Passed
  • Unexecuted
  • Custom Status


Test Run Project and Test Case Project Names Visible in Jira

The name of the project where a Test Run was executed and the name of the project where a Test Case was created are now visible in the qTest: Test Execution iframe in Jira.
This enhancement is beneficial for customers who use Shared Test Cases, as it allows you to see the name of the original Project where the Test Case was first created along with the name of the Project where the Test Run was executed.


Auto-filter Linked Test Runs in Jira

A new checkbox has been added in the Release Integration Settings of qTest Manager that automatically filters your list of Test Runs on the qTest: Test Execution iframe in Jira. The filter matches your linked qTest Test Runs with the Fix Version/Sprint of that Jira issue.

For each Test Case visible in the Jira issue, the status for the last executed Test Run matching the filter, replaces the Last Execution Status of the Test Case. If no Test Runs match the filter, you will see the message "There's no Test Run matching your filter."
Note: this new checkbox will be selected by default. You can deselect this checkbox if you choose.

Known Limitations
Sometimes the qTest:Test Execution iFrame in Jira does not load completely upon the first time opening the Jira issue, therefore you will need to reload the page. Jira Test Management plugin v6.11.10 will be released to fix this issue.


Configure Password Requirements

As a Site Admin, you can now configure your qTest password requirements to follow stricter guidelines. The current default password policy follows these conditions, ‘Password must be no less than 8 and no more than 16 characters, include at least one number and one letter.’
To change the default password requirements to a custom policy, please read this article


De-support TLS 1.0 and 1.1

qTest support for TLS versions 1.0 and 1.1 is being discontinued on December 20, 2018 in order to stay aligned with modern security practices. Customers that use qTest products need to upgrade to TLS 1.2 or later. This includes web browsers and external applications that are integrated to qTest.

  • What does this mean?
    There may not be any changes necessary. If you are already using up-to-date browser versions, you are probably already using TLS 1.2 or later.
  • Am I affected?
    All qTest products, including calls to qTest APIs, are impacted by this change:
  • Browsers
    You will be unable to access qTest products on outdated browsers, so please make sure your browsers are up-to-date:
    • IE 11
    • Firefox 27+
    • Chrome 30+
    • Safari 7+
  • Integrated applications
    Any web application calling qTest APIs and attempting to make a connection using TLS 1.0 or 1.1 will no longer work, so please double-check to make sure your integrated applications are connecting using TLS 1.2 before December especially if that application is on an old version.
  • Jira Server - qTest OnDemand integration
    As stated in our End of Support Announcements for qTest, qTest is officially compatible with Jira Server v7.2+. If for some reason you’re not able to upgrade to Jira Server v7.2, and you’re still running on Jira Server v6.4 or older, you may still have Java 7 installed. In this case, we recommend upgrading to Java 8 or configuring Java 7 with the workaround mentioned here: TLS and Java.

Please contact with any additional questions.

Manage Project Settings Permission Updated

The Manage Project Settings Permission has been updated and now includes additional options that a user can be granted access to or not. If a user is currently granted the Manage Project Settings permission, then all permissions listed below will be selected by default. However, you can customize these permissions if you choose.

You can access these permissions from either of the following pages:

  • Administration>User Profiles
  • Project Settings> User Management


Saved Queries 

Custom Data Queries that have been created and saved are now visible when creating a Test Run and selecting the ‘Data Query View’ button. An alert will display for queries that cannot be used to create Test Runs. Only custom queries, in the ‘My Queries’ section, are visible.

Firefox 62.0.2 Compatibility

The qTest Integration Browser Plug-in is now compatible with Firefox versions 62.0.2 and beyond.

Legacy Java SDK Updated

The legacy Java SDK has been updated to wrap the API so that you can submit multiple automation Test logs. These API’s return the Job ID.
The following API’s have been wrapped:

  • POST /api/v3.1/projects/{projectId}/test-runs/{testRunId}/auto-test-logs
  • POST /api/v3/projects/{projectId}/auto-test-logs

After batch submitting Test Logs, you will need to use the following API to check the progress status:

  • /api/v3/projects/queue-processing/{id}


You can now retrieve the Target Release/Build’s field ID so you can use it when creating or updating Test Runs. The following API is enhanced:

  • GET /api/v3/projects/{projectId}/settings/test-runs/fields

The Target Relase/Build’s field ID is now available when creating, updating, or retrieving data of a Test Run. The following API’s are enhanced:

  • modify a Test Run's Target Release/Build property
    PUT /api/v3/projects/{projectId}/test-runs/{testRunId}
  • set a value for the Test Run's Target Release/Build field when creating it
    POST /api/v3/projects/{projectId}/test-runs
  • retrieve Target Release/Build property of a Test Run
    GET /api/v3/projects/{projectId}/test-runs/{testRunId}
    GET /api/v3/projects/{projectId}/test-runs
Powered by Zendesk