qTest 7.2.3 OnPremise Release Notes - February 3rd, 2016

Installation packages

Docker – Deployment package

  • New installation package, including qTest Insights, on Linux server

  Note: We support Docker version 1.6+

Linux (non – Docker) upgrade package

One package to upgrade qTest components:

  • qTest: upgrade qTest from version 4.x, 5.x and 6.x to 7.2.3
  • qTest Sessions: upgrade qTest Sessions from version 2.0.8 to 2.2.2

  Note: We support CentOS 6.4 Final – 64 bit or Ubuntu 12.04 – 64 bit

Windows installation packages

  • New installation of qTest version 7.2.3; and upgrade qTest from 4.x, 5.x, and 6x to 7.2.3
  • New installation of qTest Sessions version 2.2.2; and upgrade qTest Sessions from 2.0.8 to 2.2.2
  • New installation of qTest Insights version 3.0.1; and upgrade qTest Insights from 1.2.9 to 3.0.1

Plugin Updates

To take advantages of new features and enhancements in this release, please install or upgrade our qTest plugins:

New Features

Manage Active Sessions

  • Users with the site admin role can view and terminate active user sessions. If a user’s session is terminated, they will be redirected to the qTest login page.

  • The site admin can also configure the system to automatically terminate a user’s session when they have been idle for a specified amount of time. They will receive an alert before their session is terminated

  Important: Users can have a maximum of 3 active sessions. After reaching the session limit, users will not be able to login to qTest. When the session limit is reached, users can manually terminate their sessions to restore their access to qTest

Cross Project Reporting

This feature is only available in the qTest Elite edition. Cross Project Reports allows you to configure and view reports with data from multiple projects. The Test Execution Summary, Testing Velocity and Execution Status with Defects reports are available in Cross Project Reporting.

    • Users must create project groups for Cross Project Reports. Since each project has its own Field Settings and those settings may vary across projects, you will need to map Test Run Status, Release and Defect Status of the project group with the values defined in each project

    • A project group can be shared with individual users or user profiles:

      • Shared with individual users, users can view Cross Project Reports in the Report tab of any projects that they have access to
      • Shared with specific user profiles, users can view Cross Project Reports in the Report tab of any projects that they have access to with the specified profile(s)
    • You can view the Cross Project Reports of project groups that you are a member of, in the Report tab of any of your accessible projects

Integration with Jenkins or Bamboo

qTest Premium and Elite editions now provide integration with both the Jenkins and Bamboo continuous integration (CI) tools, which collect and report JUnit test results from your builds to qTest.

    • In qTest, you will need to activate the CI Tool Integration feature to receive test results submitted from your CI server

        Note: Activating the CI Tool Integration feature will also activate the qTest Automation feature. You will need to map the JUnit test result values with the Test Execution status values in qTest

    • On the Jenkins/Bamboo CI server side, it is required that you install our qTest plugin. Once installed, the plugin will collect JUnit test results from your builds and submit them as Test Runs and Test Logs to qTest. The qTest plugin supports any testing frameworks which are capable of generating JUnit XML format test reports

        Note: If your testing framework does not generate JUnit XML format test reports, you can utilize the xUnit Plugin to generate and publish test results before the qTest Plugin collects and reports the results to qTest

    • After installing the qTest plugin, you can set up a post build action (in Jenkins) or a task (in Bamboo) and configure the connection to your qTest project
    • We offer 2 options to get unit test results:

      • Parse test results from testing tools (default)
      • Utilize test results from the CI tool

          Note: this option is only available for Jenkins

    • On the Test Execution tab of your qTest project, you can export an Excel file to view details of tests submitted from your CI server, including 2 views: Build by Build, and Test by Test

    • On your CI tool side, we provide a report allowing you to track the status of test submissions to qTest after each build is completed

TestLink's Test Cases Conversion Tool

    • The tool converts TestLink's Test Cases in XML format to qTest importable Excel files
    • Download it from qTest's Resources page


Test Execution

1. Mirror folder structure from Test Design tree to Test Execution

    • You now have the option when adding Test Runs from Test Cases to duplicate the folder structure from Test Design. Modules with sub Modules will be created as Test Cycles. Otherwise, Modules will be created as Test Suites

  • This option is disabled in the following cases:

    • You are adding new Test Runs to a Test Suite
    • You are selecting Test Cases
    • Selected Modules are in different parent Modules
    • You are selecting configurations to add Test Runs

2. Linked Defect information

    • In the Test Execution tab, you can now view the linked Defects of Test Runs under a Release, Test Cycle or Test Suite page

    • You can also view the roll-up of linked Defects from Test Steps to Test Logs and to Test Runs

Test Design

  • Browser spell and grammar check is now available for the Test Step fields

JIRA Integration

1. Linked qTest Test Runs displayed in JIRA issues

    • From JIRA, you can view an issue’s linked qTest Test Run information and the last 5 Test Logs of the Test Run
    • Test Execution information is only shown on JIRA issues which are configured to be Defects in qTest and in projects which are integrated with qTest

2. Defect Submission’s Auto fill

    • In the JIRA integration settings section, the Defect Description field is configured with the Session Description, Session Environment and Description (Test Steps) fields by default. The default configuration will only apply to new JIRA integrations

  • Auto fill settings are applied when you execute Test Runs with Quick Run

VersionOne Integration

    • qTest now supports creating integration connections to a VersionOne project using an access token. This is only available from VersionOne Winter 2015 onwards

LDAP Integration

  • LDAP over SSL connection is now supported
  • Your qTest instance can integrate with multiple LDAP systems. As the site administrator, you can import or merge existing users with users from different LDAP systems. An individual user can only be authenticated with one LDAP system at a specific time
  • Once the user is authenticated with an LDAP system, they can use either their LDAP username or qTest email, with their LDAP password to login to qTest

      Important: When logging in to Web eXplorer, it is required that you use your qTest email with LDAP password.

Site Admin – User Profiles

    • When a user profile is updated in the site administration section, changes will now be applied to all users that are associated with that profile

Project Settings – User Management

  • As a project admin, you can select multiple users to remove from a project by selecting Ctrl + Remove

Data Queries

  • Automation Test Case has been added to the criteria options for the Test Design data query
  • Automation Test Run has been added to the criteria options for the Test Execution data query

Session Editors

  • Annotation format will be retained per annotation type

Supported Browsers

  • IE9, IE10 and IE11
  • Chrome
  • Firefox
  • Safari


  • qTest objects can now be accessed using the following URL format: [your qTest URL] /p/[project-ID]/portal/project#key=[Object PID]


    • Session objects cannot be accessed with a URL
    • PID is case-sensitive
  • Rich Text Editor fields will now support text wrapping
  • Rich Text Editor fields will now support text wrapping

New APIs

  • New Login API is available

      Important: The existing login API will be deprecated in our next OP release.

  • Logout API to revoke a session token


    • It is highly recommended that you logout of your API session when it is completed
    • One user can have a maximum of 3 web and API sessions. When you reach the maximum number of sessions, you cannot login to qTest. In order to restore access to qTest, you can manually terminate your active sessions when logging into the qTest web application or contact your site administrator
  • Get the requirement traceability matrix report via an API

Please review the APIs document for further details.

Known Issues

Cross Project Reporting

  • For projects integrated with external defect trackers, the reports will show no defect information
  • You are required to map the project's defect status even when it is integrating with an external defect tracker

Integration with Jenkins or Bamboo

  • On configuring the qTest Plugin in your CI tool, the selected Environment only affects newly created Test Runs. It will not update the existing Test Runs with the new Environment
Powered by Zendesk