6.1 qTest 7.0 Release Notes - Dec 14th, 2015

New Features

Managing active sessions

    • As a site admin, you can view and manually terminate active sessions. If a user’s session is terminated, he will be redirected to qTest login page.

  • You can also configure the system to automatically terminate sessions after being idle for a specific amount of minutes. It will inform users 5 minutes before their sessions are terminated.

Cross Project Reporting

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

    • Users can create multiple project groups, to customize project data views for the Cross Project Reports. Since each project has its own Field Settings and 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 users so they can view the Cross Project Reports.
      • 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

In this release, qTest features the integration with these 2 continuous integration (CI) tools, which collect and report JUnit test results from your builds to qTest.

It is available in qTest Premium and Elite editions.

    • On the qTest project side, you will need to activate the CI Tool Integration feature in order to receive test results submitted from your CI server.

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

    • On your 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.
    • After installing, you can set up a post build action (in Jenkins) or a task (in Bamboo) and configure the connection to your qTest project.

    • 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.

Test Execution Enhancements

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

    • You will 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 Enhancement

  • Browser spell and grammar check feature is now available when defining Test Steps

JIRA Integration Enhancement

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.

        Note: It is required that you upgrade our qTest plugin to the latest version on your JIRA instance.

    • Test Execution information is only shown on JIRA issues which are configured to be Defects in qTest

Session Editor Enhancement

  • Annotation format will be preserved per annotation type.


  • New API: get requirement tracebility matrix report.

Please check our APIs document for details.

Known Issues

Cross Project Reporting

  • For projects integrating with external defect trackers, the reports will show no defect.
  • 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 qTest Plugin in your CI tool, the selected Environment only affects the newly created Test Runs. It will not update the existing Test Runs with the new Environment if you have selected a new one.

Linked qTest Test Runs displayed in JIRA issues

  • It requires a login to qTest in order to display the linked Test Runs.