5.5 qTest 7.6.0 On Demand Release Notes - May 23rd, 2016

New Features

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

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

  1. The option is disabled if you select multiple objects

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

New APIs

  • Query Requirements, Test Cases, Test Runs and Defects
  • Query history of Requirements, Test Cases, Test Suite, Test Runs and Defects
  • Create an association between objects
  • Remove an association between objects
  • Query comments
  • Retrieve associated Defects of Test Logs or Test Step Logs

Enhancements

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 to automatically organize requirements into folders. Epic Name is a new JIRA field distinct from the Epic Link field, which is still select-able

  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

Bug Fix

  1. Changing a Test Cycle’s Target Release/Build will not change the assignees of Test Runs which are located directly under the Test Cycle

Known Issue

  1. Test Execution section is empty in JIRA issues when using Safari on MacOS. We will release the fix for this soon