qTest 8.1 OnPremise Release Notes - Nov 28, 2016


  • The Master token will be deprecated in our next release

Installation/Deployment Packages

Linux Docker deployment packages

  • One Docker deployment package to deploy or upgrade all qTest components, including qTest, qTest Sessions, qTest Insights (2.0) and all prerequisite softwares
  • One separate package to deploy qTest Insights (2.0)

Linux non-Docker upgrade package

  • One installation package to upgrade qTest and qTest Sessions

Windows installation packages

  • One installation wizard to install or upgrade qTest
  • One installation wizard to install or upgrade qTest Sessions

Plugin and Package Updates

It is highly recommended that you use the latest version of our plugins and packages:

  • qTest plugin for Bamboo - version 1.3.0
  • eggPlant Connector - version 1.1.0

New Feature

qTest Navigation Change – qTest Sessions, qTest Insights, Project Settings

You will notice a slight change in the qTest navigation header. For a better user experience, we have moved project setting next to user profile, and created a new icon where users can access qTest Sessions and qTest Insights 2.0


New qTest Sessions UI/UX for qTest eXplorer Users

For those using qTest eXplorer, we have built out a brand new UI/UX to create, execute, and review all test sessions. The new qTest Sessions experience will include better search, tagging and tracking capabilities along with a brand new feature for automated script generation for Selenium and Protractor frameworks.


Single Sign-On (SSO) Integration

This feature allows site administrators to integrate qTest with a SAML2 Identity Provider (IdP) and users to log in to qTest with their SSO credentials. This feature is available in our Enterprise and Elite editions.

  NOTE: For now, the integration with OKTA is officially supported.

To enable this feature, you will first need to configure the integration with your IdP.

  1. In Administration section, select tab Authentication Integration on the top navigation and then select SSO in the left pane
  2. You are required to enter the URL to your IdP metadata. Alternatively, you can upload an IdP metadata XML file from your local machine
  3. Switch on the Activation Status and then click on Save button

qTest - Admin - Authentication Integration - SSO Config

There are 3 ways to allow qTest users to log in with SSO credentials:

  1. Invite a new user: you are required to enter both qTest email and SSO username
  2. To allow an existing qTest user to log in with the SSO credentials:
    • Change the Authentication System to the integrated IdP
    • Then you are required to enter the corresponding SSO usernname
  3. To save effort, while configuring the integration, you can select option Create new account on qTest upon user's first login
    • If users log in to qTest for the first time, they are required to enter additional information to create qTest account before accessing qTest
    • If there has already been a qTest account with the same email, the user is allowed to merge with the qTest user. This is only applied with the emails we receive from the IdP. In case the user manually enter his email, he will not be able to merge

To log in with SSO credentials, on qTest Login page, click on Login with SSO button

Automation Integration

This release features the integration with eggPlant and UFT. We provide command line tools which are capable of executing automation scripts and reporting results back to qTest.

eggPlant Integration

  • The command line tool will collect test results in JUnit-compatible format. There are 2 options to execute the tool:
    • Launch eggPlant script and then report the results to qTest
    • Only collect and report existing results to qTest
  • You are required to input the test suite directories whose test results you want to report to qTest. You can specify multiple test suites. You also have a choice to submit all existing logs or only the latest ones
  • If an eggPlant command is specified, the tool will launch eggPlant scripts first and then report the results to qTest
  • You can also specify a Module and a Test Suite in which Test Cases and Test Runs will be located in qTest
  • The configurations are stored in a text file so that they can be reused any time you execute the tool
  • The tool will not report the results of aborted scripts to qTest


  • eggPlant Functional needs to be installed on the same machine in order for the integration tool to kick off eggPlant scripts
  • The integration tool works with eggPlant Functional v16.01

UFT Integration

  • The command line tool will kick off UFT scripts and then report results back to qTest
  • In order to collect UFT results in qTest, the UFT scripts must be kicked off using the command line tool
  • You can specify a Module and a Test Suite in which Test Cases and Test Runs will be located in qTest
  • Currently, one UFT test is mapped as a Test Case in qTest while its actions are mapped as Test Steps
  • The configurations are stored in a text file so that they can be reused any time you execute the tool


  • UFT needs to be installed on the same machine in order for the integration tool to kick off UFT scripts
  • The integration tool works with UFT v12.52


Jenkins Integration

  • By default, a qTest Test Case is created from a JUnit Test Suites (Class). Now there is an option to create a qTest Test Case from a JUnit Test Cases (Method)

  NOTE: In order to use this enhancement, please install the new version of the qTest Jenkins plugin

Jenkins - qTest build action - Mapping Test Case

JIRA Integration

Support setting up JIRA Integration in qTest using JIRA OAuth token

  1. On Add Connection dialog, after you have input the Server URL, click on Use JIRA OAuth
  2. Click on the Authorize URL
  3. Get the verification code
  4. Input verification code on the dialog and click Submit
  5. Username will be auto-filled with "apikey" and Password will be auto-filled with the OAuth token
  6. Test and save the connection

qTest - Project Settings - Integration Settings - Add Connection

Test Design

  • When moving or coying items to a shared Modules, qTest will not ask you to confirm if you want to share these items for the below cases. They will remain the same
    1. Test Cases are being moved or copied from shared Modules
    2. Modules being movied or copied are already shared

Test Execution

  • On Data Query View of Create Test Run dialog, you are now able to share your saved queries so your team members can re-use them
    qTest - Test Execution - Add Test Run - Data Query View - Team  Queries
  • URLs in Test Log notes are clickable
  • When executing Test Runs, qTest will prompt you if new unapproved versions are available


  • In Administration section, Project ID is added to Project grid
  • New custom field type: Mmultiple selection combo box, is available to create a Custom Field in Field Settings. Users can select multiple values for this type of field, and perform contextual search on the field
    qTest - Field Settings - New custom field type
  • We provide new options for you to download exported Excel files without cell merging. They would be helpful for you to generate your custom reports
  • Time zone is automatically updated according to Daylight Saving. It is recommended that you check your selected time zone in My Profile page

Bug Fixing

  • Bamboo Integration: support Bamboo projects with multiple branches
  • Automation Integration v2: Null Pointer Exception will not be thrown after a scheduled automation test starts while another test in progress
  • Copying text from objects' Properties section will not trigger "unsaved work" message
Powered by Zendesk