5.3 qTest 7.7.x On Premise Release Notes - June 15th, 2016

Installation/Deployment Packages

Linux Docker - Deployment package

  • New installation package, including qTest, qTest Sessions, qTest Insights and Scenario, on Linux server

  NOTE: We support Docker version 1.6+ on CentOS 6.4 Final – 64 bit or Ubuntu 12.04 – 64 bit

  NOTE: Starting with qTest 7.7.x, in order to upgrade on a Linux server, it is required to upgrade using the Docker deployment. 

Windows installation packages

  • New installation of qTest version 7.7.x; and upgrade qTest from 6.x and 7.x to 7.7.x
  • New installation of qTest Sessions version 2.2.2; and upgrade qTest Sessions from 2.x to 2.2.7
  • New installation of qTest Insights version 3.0.2; and upgrade qTest Insights from 3.0.1 to 3.0.2
  • New installation of qTest Scenario version 1.2

Plug-in Updates

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

  • qTest plugin for JIRA Server v6.11

New Features

Administration

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

Custom date format

As a site administrator, you can select a date format to be displayed across different qTest modules for your users.

  • In Site Administration, select System Configurations tab
  • In Internationalization section, select one of the available date formats
    qTest - Site Admin - System Settings - Internalization
  • Click the Save button to apply the format to your qTest site
  • The selected date format is applied to all date values displayed in qTest pages, reports, and exports, except for exported csv files

Common

Filter on left navigation pane

    • You can apply filters to narrow down items on Test Plan, Requirements, Test Design and Test Execution tree
    • On the tree's toolbar, click on Filter icon and then select Set Filter option
    • On Filter dialog, you will have various criteria to filter the navigation tree
    • The multi-select fields support “Type Ahead” search functionality, to display items matching the text entered in the field

qTest - Test Execution - Filter

Data Query - Query for items in a selected container on the navigation tree

    • Right click on a container on the navigation tree and select Data Query from the context menu
    • A criterion is automatically added so that you can query for items under the selected container
    • This option is disabled if multiple containers are selected
    • For example: If you click on a Test Suite in Test Execution tree, and then select Data Query, then the Data Query will be generated to show Test Runs within that Test Suite

qTest - Test Execution - Context Menu - Data Query

Test Design

Test Case Conversion

This new feature allows the user to convert manual Test Cases to automation Test Cases (and vice versa) so that existing manual Test Cases can be tied to automation test results.

  • In order to convert individual Test Case, on a Test Case page, click Convert button on the top left corner
    qTest - Test Design - Test Case - Convert button
  • You can also convert multiple Test Cases at one time:
    • Select multiple Test Cases from the Test Design tree, right click and then select Convert option. If a Module is selected, the Convert option is disabled
      qTest - Test Design - Test Case - Tree - Context Menu - Convert
    • Alternatively, select Test Cases from the Test Cases Data Query result and then click on the Edit drop-down and the Batch Convert button
      qTest - Test Design - Test Case - Data Query - Batch Convert
    • In the Batch Convert modal, select Test Case type (manual or automation) and click Confirm button to start the converting progress
    • After it is completed, click on the OK button to close the modal
    • If a manual Test Case is converted to automation, click the Input Automation Content button to fill in the Automation Content for converted Test Cases. It is optional
      qTest - Test Design - Test Case - Input Automation Content
      qTest - Test Design - Test Case - Input Automation Content 2
    • The Automation Content is the identifier that is used to point automation execution results to a Test Run linked to this Test Case

View Execution History of a Test Case or a Module under Test Design tab

  1. Right click on a Test Case or Module, then select View Execution History option
    qTest - Test Design - Context Menu - View Execution History
  2. The system will open Test Execution Data Query for you to view associated Test Runs of the selected object. The most recent Test Run status will display in the Query Results
    qTest - Test Design - Context Menu - View Execution History - Data query result
  3. The option is disabled if you select multiple objects

Enhancements

Test Execution

Notification Settings

    • You can select some specific Test Execution Status values to trigger the notification event
    • You can also configure to send notification emails to the Assignee of the Next Test Run or Subscribers of the Next Test Run within the same Test Suite of the executed one
    • This feature can be useful for integrated testing that requires different testers to execute Test Runs in a specific sequence. This “Ready for Next Tester” notification can be used to notify the Assignee of the Next Test Run as soon as the previous Test Run is executed with a specific status, for example: “Passed”

qTest - Project Settings - Notification Settings - Test Run - New Event

Test Run Assignment view

  • On Test Execution’s root page, Assignment section is replaced with Test Run Assignment view to allow the user to easily see all of their assigned Test Runs
  • By default, it shows all your assigned Test Runs
  • You can apply filtering and sorting on the grid
  • You can also Run or Quick Run selected Test Runs

View of Test Case properties from Test Runs

    • In addition to Test Run properties, you are now able to view associated Test Case properties from a Test Run page
    • These Test Case fields can be used to query for Test Runs. The Test Run Query results grid can be customized to include Test Case fields

qTest - Test Execution - Test Run - Test Case Properties

  NOTE:

  • The system will always display the latest Test Case properties, regardless of the Test Case version associated with the Test Run, except for Description and Precondition. We will enhance this in a future release to show the Test Case properties values that correspond to the Test Case version that is selected

Test Run Detail Report includes associated Test Case information

When exporting the Test Run Detail report, you can now select the associated Test Case information for the spreadsheet, including:

    • Test Case ID
    • Test Case Automation
    • Test Case Automation Content
    • Test Case Name
    • Test Case Status
    • Test Case Type
    • Test Case Assigned To
    • Test Case Description
    • Test Case Precondition
    • Test Case Priority
    • And any Test Case custom fields

qTest - Test Execution - Export Test Run details 2

Test Design

  • You can copy and paste Test Cases and Modules across projects. This feature is only available for the Elite package

Reports

Defect Analysis

    • This report can be filtered by Status and one of the other fields, including Priority, Severity, Assigned To, Submitter and Module

qTest - Reports - Defect Analysis - Report Settings

Sessions

Remember Zoom Level when editing Session in Session Editor

  • When editing Sessions, the Zoom level of a screenshot is retained when navigating to other screenshots

Link Session Defect to the Test Run

  • When submitting a Defect from the Session Editor, the Defect will be linked to the Test Run which the session was launched from or associated with
  • The defect will appear in the Session's detail page as well as in the Test Run's

Session Editor's Test Case Preview dialog

  • All screens option is selected by default
    qTest - Sessions - Session Editor - Test Case preview dialog
  • Ability to view individual screenshot
  • Ability to toggle the visibility of test case fields
    qTest - Sessions - Session Editor - Test Case preview dialog - Toggle test case field
  • Test modules enhancements
    • Ability to filter test modules by typing text in the Test module field
    • Test modules are now displayed as tree-like structure, which makes it easier to navigate/collapse/expand
    qTest - Sessions - Session Editor - Test Case preview dialog - Test module

Test modules enhancements

  • Ability to filter test modules by typing text in the Test module field
  • Test modules are now displayed as tree-like structure, which makes it easier to navigate/collapse/expand

JIRA Integration

Display Associated Test Case, Test Run, and Test Log information on linked JIRA issues (Requirements and Defects)

    • Test Case and Test Execution information is displayed on JIRA issues which are configured to be Requirements or Defects in qTest
    • You can view the information below:
      • Associated Test Cases with their latest execution result
      • Associated Test Runs with the 5 most recent Test Logs of each Test Run

JIRA - Test Execution

Organize JIRA Requirements by Epic Name field

  • When configuring requirements imported from JIRA, you can now select Epic Name as one of the two JIRA fields when you select the JIRA type as an Epic. This field will automatically organize requirements into folders . Epic Name is a new JIRA field distinct from the Epic Link field, which is still selectable

  NOTE:

  • The existing Modules named after Epic ID will not be updated to Epic Name
  • Changing Epic Name in JIRA will not update the Module name in qTest

Rally Integration

  • Status of Defects in Rally are synced to qTest