Menu

Manager 9.2 OnDemand Release Notes

Manager 9.2 OnDemand Release Notes

We are excited to announce the official release of Manager 9.2 OnDemand!

Several new features have been made which increase the usability of the TestPad. Some of these include:

  • ability to view all associated defects in the Defects tab of the TestPad
  • send attachments from Test Logs and Test Step Logs as attachments to linked Jira defects
  • view and modify Test Run properties from the TestPad

Additional enhancements were made to the Jira integration, the Test Run page and many more. Please read below for further information regarding Manager 9.2.

New Features

Test Execution

Ability to Modify Test Logs

You can now modify a Test Log provided you are the Tester of the Test Log or a Project Admin. 

To modify a Test log:

  1. From the Execution History grid, select the pencil icon in the Action column which will load the Test Log to the Test Pad.
  2. A notification will display at the top of the Test Pad that indicates which Test Log number you are modifying. 
    qTest_Manager_9.2_OnDemand_Release_Notes_-_July_30__2018.zip.png
  3. Once the Test Pad loads, you can modify the following Test Log data:
    • Test Log properties
    • status of the overall Test Log or each Test Step Logs (this will automatically update the Executed End Date to when you save the modification)
    • Link Defects
    • Add or remove attachments of the Test Log or Test Step Logs
  4. Save your changes.
  5. In Execution History, an asterisk will appear next to the Test Log number as a visual indicator that the Test Log was modified.

    IMPORTANT: You cannot modify the following items as they would create a new Test Case version:

    • Test Case description and precondition
    • Test Step description and expected result
    • Re-order, add or remove Test Steps
    • Add or remove Test Step attachments 

    image1.png

Jira Integration

Send Test Log Attachments to Linked JIRA Defects

Attachments for Test Logs and Test Step Logs can now be automatically uploaded to linked Defects in Jira. This feature is enabled by default, but you can disable it by selecting the 'send attachments' checkbox in the JIRA auto-fill defect fields dialog. You will need to enable this feature in your Jira Configuration Settings
image5.png

  • If you link a Defect to a Test Log, attachments of the overall Test Log and each Test Step Logs will be uploaded to the Defect.
  • If you link a Defect to a Test Step Log, only attachments from the Test Step Log and its previous steps are uploaded to the Defect.

Attachments sent from qTest will have the following identifiers in the JIRA Defect:

  • a prefix of "qTest" or "qTest_[Test Step#]"
  • comment with the name of the attachment and the qTest user who sent the attachment
  • comment in the event the attachment failed to upload properly

The maximum attachment size for qTest is 50MB, so you will need to configure your "JIRA Attachment Size" to be at least 50MB. If you remove an attachment in qTest, it will not remove the corresponding attachment from JIRA.

API's

The following are new API's:

  • Add attachments to a Test Step Log.
  • Remove attachments from a Test Step Log.
  • Download attachments from a Test Step Log.

Enhancements

Test Execution

New Test Step Log Attachment Option and Column

A new option is available that allows you to upload an attachment to a Test Step Log without adding an attachment to the corresponding step of the Test Case. Previously, when adding an attachment to a Test Case step, a new Test Case version would be created.

You can upload attachments to a Test Step Log while:

  • Executing a Test Run in the TestPad
  • Viewing an executed Test Log from Execution History

Additionally, a new column is available for the Test Step Log in Test Execution that displays a 'paper clip' icon to indicate when an attachment is available for the Test Step Log.
image6.png

Upload Screenshots from Clipboard

You can now paste screenshots from your clipboard to the Upload Attachments dialog of the Test Execution Tab. You can utilize any screen capture tool to add the screenshot to your clipboard.

Note: This feature will not work for Safari, IE or any browser running on MacOS.

image3.png

View and Modify Test Run Properties from the TestPad

You are now able to view and modify Test Run properties from the Test Run page while executing a Test Run in the TestPad. The changes will save to the latest Test Run properties and the Test Log being executed.

image8.png

View Linked Defects

You are now able to view all Defects linked to previous Test Logs or Test Logs of sibling Test Runs. These will display in the Defects tab of the TestPad. (Sibling Test Runs are considered to be other Test Runs from the same Test Case.)

view_inked_defects.png

Test Runs

Display Rich Text Formatting

Rich text formatting applied to Test Run Fields and Linked Jira Defect Fields will now display in the areas below

Test Run Field Areas

  • Test Runs grid of Release/Test Cycle/Test Suite
  • Execution History grid
  • Test Log Details grid

Update to the Test Run Page Attachments Tab

The Attachments tab located on the Test Run page has been updated to display the Attachment preview thumbnail, as well as the Attachments Grid. This allows the information displayed on the Test Run page to stay consistent with the information provided in the Attachments tab on the TestPad.

attachments_tab_test_run_page.png

 

Jira Integration

Jira Webhook Update

The Jira Webhook now includes a JQL which reduces the number of signals sent to qTest from the webhook when an update is made in Jira. Previously, for example, if only a Jira Story is configured as a qTest Requirement, but a task was updated in Jira, the webhook would still send a signal to qTest, although one was not needed. This change reduces unnecessary traffic from Jira to qTest.

As a result of this change, there is a known limitation:

If a Jira Issue is synced to qTest but moved to another project or issue type in Jira that is not configured with qTest, it will become out of sync in qTest until you select the "Retrieve button" to manually sync data from Jira to qTest.

Jira Global Admin Permission

From 9.2 and later, the Jira Cloud integration will require a user who changes the config in qTest to have the Global Admin permission so that qTest can update the webhook. Therefore, you cannot revoke the Global Admin permission from a users integrated account.

Previously, if a user who set up the qTest connection assigned with the Global Admin role, and then the Global Admin permission was revoked, the integration would work fine. Now, the Jira Global Admin permission cannot be revoked for the user who established the connection. If it is revoked, the qTest Test Execution iFrame that displays on a Jira issue will not be displayed. 

Enhanced History Tab of Jira Requirement

When a linked Jira Requirement is changed in Jira, qTest will update the content on the linked Requirement, including logging an entry in the Requirement History. Entries in the History will show the qTest username to indicate who it was “Changed By.” 

  • If a Jira Requirement is automatically synced, it is recorded as having been updated by “Jira Integration.”
  • If a user manually clicks the Retrieve button to update a Jira Requirement, he/she is recorded as the user who made the change in the Requirement.

In addition to the qTest fields, changes to all Jira fields are recorded in the History tab with the Jira logo next to the Jira Field Name.

Known Limitation: Given you created a new custom field in Jira, but have not clicked the "Refresh Field Settings" button to sync the new field to qTest, and there is a Requirement change in qTest with the new field, a record will display in the History tab as "No change." Once you select the "Refresh Field Settings" button, qTest will begin storing the field value in our database and the History tab will show the value change accordingly.
jira_history_tab.png

Display Rich Text Formatting

Rich text formatting applied to Test Run Fields and Linked Jira Defect Fields will now display in the areas below.

Linked Jira Defect Field Areas

Only applicable to description and comment fields of linked defects from Jira in the following sections:

  • Defect Summary
    • Release
    • Test Cycle
    • Test Suite
  • Defects Tab
    • Test Run
    • TestPad

 Progress Bar when Manually Fetching Jira Defect Data

A new progress bar has been added to the Jira Integration Configuration page that displays the total number of Defects that are being retrieved when you click the 'Fetch Jira Defects' button. You can close the dialog box without interrupting the 'fetch' as the process is handled in the background.

jira_progress_bar.png

Rally and Version One Integrations

You are now able to customize Defects grids with all fields from Rally or Version One. You can customize the Defects grid in the following areas:

Defects Tab

  • Test Run
  • TestPad

Defect Summary Tab

  • Test Suite
  • Test Cycle
  • Release

You can also drag and drop the columns to reorder, however, the ID column cannot be moved. Once a column order is set, it will remain static on all other Defect grids until you change the order again. Select the 'gear' icon in the Defects tab to add or remove the available fields.

Known Limitation: Rich text formats visible in Rally/V1 data will not display correctly in qTest, and will appear as html tags. It is recommended you do not include Rally or Version One rich text editor fields in your Defect Summary grid or Defect Tab. 

General 

Progress Notification when Copying Objects

A progress notification will display when you copy/paste more than 20 objects (Requirements, Test Cases or Test Runs) or at least one container (such as Module or Test Suite) on the left, folder tree. The notification will provide the total number of objects being copied.

image9.png

Bug Fixes

  • Ticket 15933: Hyperlinks available in a Rich Text Editor or URL Field of a Test Run.
    • Rich Text Editor Field: right-click and select open in a new tab/window.
    • URL Field:
      • View Mode-click directly in the link to open in a new tab, or right-click to open in new tab/window.
      • Edit Mode-URL will not be clickable until you select the 'checkmark' icon to save
        Note: This functionality existed on other objects. This was a bug fix to implement expected behavior on these Test Run fields. 

 

Powered by Zendesk