Menu

Manager 9.1.5 On Premise Release Notes-June 2018

 

TestPad Enhancements

Below are highlights for each of the TestPad enhancements. For more info on using the TestPad, check out these articles: Executing Test Runs and Submit Defects in Test Execution

Rich-Text Editor

A rich-text editor has been added to the Test Step fields in the TestPad to provide additional formatting options such as bold, underline, and text color. Select the ‘A’ icon to display the rich-text editor, in the following Test Step fields:

  • Description
  • Expected Result
  • Actual Result

The rich text editor has also been included for Test Step Fields found in the Test Case Details Page of Test Design.
Note: When you view steps formatted with the rich-text editor in Data Query, Reports, Exports, History and notification emails, the rich text format is removed.

image-0.png

 

Attachments Tab

The Attachments Table and Attachment Preview have both been updated to provide you with additional information.

Attachments Table:

The Attachments Table now provides the following details:

  • The user that uploaded the attachment
  • Date of upload
  • Type of attachment  ex: Test Log or Test Case

Attachments Preview:

You can now preview the attached image/file in the bottom panel by selecting the attachment name in the Attachments Table. Alternatively, you can select the backward and forward buttons to navigate through the available attachments.
Note: PDF and Excel will not display the image in preview mode. You will need to download these to view.

image-1.png

Time Tracking Auto-Calculation

Previously, when logging your execution time, you had to manually enter the planned and actual time. Now, when you save a Test Log, the Time Tracking dialog will display with an auto-calculated execution time based on your start and end time. You will have the ability to modify the auto-calculated value.

This new functionality is in addition to being able to manually enter the planned and actual time. If you have logged your execution time on the TestPad, the manually entered values will override the auto-calculation.

If the Time Tracking setting is enabled to automatically calculate your execution time the execution time is synchronized from the time tracking auto-calculation to what is displayed in the Time Tracking tab.

 

image-2.png

Test Case Precondition

The Test Case Precondition is now displayed as step #0 in the Test Step grid. This allows for greater visibility to any preconditions that may be required before testing begins. Previously, you were required to select the Precondition Tab to enter and view this information.

image-3.png

Test Step Display

The TestPad is now able to display up to 200 Test Steps per page. Previously, the maximum number of steps was 50.

Once you select the number of test steps to be displayed, this is a personal user-setting and will become your default until you change it.

image-4.png

Test Step Status

You are now able to select more than one Test Step and set a status to those selected using the checkboxes to the left of each step. Previously, you were only allowed to select an individual Test Step or all Test Steps to mark a status.image-5.png

Parameters in a Test Step

You can now edit Test Step details (description, expected result or the actual result) even when there is a Parameter for a Test Step. However, you will not be able to change the Parameter value or add a new Parameter.

Test Step Details Displayed in Individual Columns

Test Step details are now individually displayed in columns on the TestPad. This allows you to easily view and enter the Description, Expected Result, and Actual Result. Previously, the Test Step details were entered in a separate pop-up widget.

You can also resize the columns in the Test Step grid to provide more or less information to be displayed in the Test Step details.

image-6.png

Auto-Refresh Test Execution Information upon Closing the TestPad

Test Execution pages (Test Suite and Test Run) will now automatically refresh with the most current test execution information when the TestPad is closed. You no longer need to manually refresh the page to display the most recent test execution information from the TestPad. Important: If you are in the middle of making changes to any Test Execution properties and have not saved, and you close a Testpad, the background page will not refresh until you confirm you want to save your changes.

image-7.png

Test Case Details Tab

The latest Test Case details are displayed in a separate tab for your reference (read-only). You are able to edit the Test Case description if you are granted the Edit Test Cases permission.
Note:If you need to modify the precondition field, this will need to be done in the Test Step Grid because precondition is now step #0 for the test steps.

image-8.png

Test Run Page

The following tabs have been updated to display the total number of items for each tab

  • Execution History: the total number of Test Logs
  • Attachments: the total number of attachments for the associated Test Cases
  • Comments: the total number of comments

image-9.png

Copy and Paste Test Cases Across Projects

You can now copy and paste Test Cases across projects, provided that the 2 projects are using the same site fields values. You can copy system and custom fields and their respective values.

Jira Enhancements

Jira OAuth

By default, the Jira integration using Jira OAuth uses our provided private and public key. Now you have the option to use your own private key to set up the connection.

Read the Connect to Jira Integration article for further information on how to set up your private key in Jira, and read the Security article for maintenance of the private key.

image-10.png

Store Unlinked Jira Defects in Manager to be Reported in Insights

You can now use Insights to report on Jira Defects that are not linked to a Test Run in qTest Manager. To use this enhancement you will need to enable Jira to provide unlinked Jira defects. You can fetch the data manually or through auto-sync which will then be stored in the Manager database. 

Therefore, 3 new fields are available in the Explore Data> Defects (Linked) report in Insights so you can filter if you would like to see your unlinked Jira Defects. The new Insights fields are as follows:

  • Unlinked Defect
  • Jira Project
  • Jira Issue Type

Note: Unlinked Jira defects will not be shown in Manager in the following areas:

  • Reports
  • Linked Defect Dialog
  • Defect Summary

To enable Jira to provide unlinked defects, do the following:

  1. In qTest Manager, navigate to the qTest project for which you would like to enable Jira to provide unlinked defects.
  2. From the Gear icon drop-down, select Integration Settings.
  3. Select Jira from the External Systems panel on the left side of the screen.
  4. Locate the Jira integration name you would like to provide unlinked defects for, and select the 'wrench' icon in the Action column. The Configure Connection page loads.
  5. In the Defect Integration section, select the "Also populate Jira defects that are not linked to Manager Test Runs" checkbox.
  6. Save and then select the Fetch Jira Defect button.
    unlinked_jira_defects_checkbox_in_manager.png
    Read this article for more information on how to Configure Jira Defects.

Deleting a Jira Bug Now Deletes the Corresponding Synced Defect in Manager

If you delete a bug in Jira, the corresponding synced defect in Manager will also be deleted. Previously, if a Jira defect is deleted, the Manager Test Log would still display the Jira link and count towards defect reporting in Manager and Insights.

General Enhancements

Firefox Integration Browser Plugin

You are now able to install and use the Firefox Integration Browser Plugin that is accessible from the Resources page. This plugin is available for Mac, Windows, and Linux operating systems and improves submitting issues to your integrated defect tracker.

User ID added to Test Log API Calls

The Test Log API now includes the UserID of the user who ran a specific test in the API.

  • /api/v3.1/projects/{projectId}/test-runs/{testRunId}/auto-test-logs
  • /api/v3/projects/{projectId}/auto-test-logs
  • /api/v3/projects/{projectId}/test-runs/{testRunId}/auto-test-logs

Field and Value Names Updated in API Calls

The following API return calls have been updated to include field and value names so that the returned API calls are more readable. 

  • Release API's
    • GET/POST /api/v3/projects/{projectId}/releases
    • PUT /api/v3/projects/{projectId}/releases/{releaseId}
    • GET /api/v3/projects/{projectId}/releases/{releaseId}
  • Build API's
    • GET/POST /api/v3/projects/{projectId}/builds
    • PUT /api/v3/projects/{projectId}/builds/{buildId} 
    • GET /api/v3/projects/{projectId}/builds/{buildId}
  • Test Cycle API's
    • GET/POST /api/v3/projects/{projectId}/test-cycles
    • PUT /api/v3/projects/{projectId}/test-cycles/{testCycleId}
    • GET /api/v3/projects/{projectId}/test-cycles/{testCycleId}
  • Test Suite API's
    • GET/POST /api/v3/projects/{projectId}/test-suites
    • PUT  /api/v3/projects/{projectId}/test-suites/{testSuiteId}
    • GET /api/v3/projects/{projectId}/test-suites/{testSuiteId}
  • Requirement API's
    • GET/POST /api/v3/projects/{projectId}/requirements
    • PUT /api/v3/projects/{projectId}/requirements/{requirementId}
    • GET /api/v3/projects/{projectId}/releases/{requirementId}
  • Test Case API's
    • GET/POST /api/v3/projects/{projectId}/test-cases
    • PUT /api/v3/projects/{projectId}/test-cases/{testCaseId}
    • GET /api/v3/projects/{projectId}/test-cases/{testCaseId}
    • PUT /api/v3/projects/{projectId}/test-cases/{testCaseId}/approve
    • GET /api/v3/projects/{projectId}/test-cases/{testCaseId}/versions
    • GET /api/v3/projects/{projectId}/test-cases/{testCaseId}/versions/{versionId}
  • Test Run API's
    • GET/POST /api/v3/projects/{projectId}/test-runs
    • PUT /api/v3/projects/{projectId}/test-runs/{testRunId}
    • GET /api/v3/projects/{projectId}/test-runs/{testRunId}
  • Defect API's
    • POST /api/v3/projects/{projectId}/defects
    • GET /api/v3/projects/{projectId}/defects/last-change
    • GET/PUT /api/v3/projects/{projectId}/defects/{defectId}
  • Query Object API
    • POST /api/v3/projects/{projectId}/search

Additionally, we have added 2 more keys to the API calls listed above.

  • field_name
  • field_value_name: the return value for a "text typed" field will be empty and the return value for a "picklist" will display the text value.

 

API's with Shared Test Cases Modified 

The following API's have been modified to provide you with all of the Test Logs for a Test Run within a shared Test Case. Details follow the API:

  • GET /api/v3/projects/{prjID}/test-runs/{test-runID}/test-logs/last-run: correct the project ID in the associated Test Case's URL and allow users to retrieve fields and values of the Test Case iif the Test Case is shared from another project
  • GET /api/v3/projects/{prjID}/test-runs/{test-runID}/test-logs: correct the project ID in the associated Test Case's URL
  • GET /api/v3/projects/42864/linked-artifacts?type=test-cases&ids=[test-run-ids]: when retrieving associated Test Runs of a Test Case, Test Runs from other projects which were created from the Test Case (if it is or was once shared to the projects) will be included
  • POST /api/v3/projects/42864/search: correct the project ID in the associated Test Case's URL

Ability to Modify a Test Log

You now have the ability to modify a Test log through the following API's:

  • Modify a Manual Test Log: PUT /api/v3/projects/{projectId}/test-runs/{testRunId}/test-logs/{id}
  • Modify an Automation Test Log: PUT /api/v3/projects/{projectId}/test-runs/{testRunId}/auto-test-logs/{id}

To retrieve data of a Test Log before modifying it, you can utilize one of our existing APIs as below:

  • Get all Test Logs of a Test Run: GET /api/v3/projects/{projectId}/test-runs/{testRunId}/test-logs
  • Get the latest Test Log of a Test Run: GET /api/v3/projects/{projectId}/test-runs/{testRunId}/test-logs/last-run
  • Get a Test Log of a Test Run: GET /api/v3/projects/{projectId}/test-runs/{testRunId}/test-logs/{id}

The ability to modify Test Logs in the UI will be released with Manager 9.2.

Improvements and Bug Fixes

  • Auto-sync of a Jira issue to Manager failed if the issue's summary contained non utf-8 characters (such as German.) This issue has been resolved.
  • Ticket 13951: After assigning selected users to projects, the selection (checkbox) in the User List grid is cleared
  • Ticket 13459: After creating an object, if you have not entered or select values for mandatory fields and try to navigate away from the object page, the system will ask you to fill values for those fields before leaving
  • Ticket 14847: Fix the issue of lost attachments on Test Steps after modifying the Test Case
  • Tickets 15376, 15686: Fix the issue of cloning duplicate values to site fields
  • Tickets 15767: Clicking More Choices to select more values when creating Test Runs with parameters will clear the default preselection
  • Ticket 15260: Fix the issue of crossed sub-domain notification
  • Tickets 16127, 16814: Make it easier to select the last Execution Status from the drop-down in the TestPad
  • Ticket 16303: Correct the prompt to enter Test Case Version in Data Query
  • Ticket 16430: Make it easier to view the last Defect in the Defect grid when adding Test Runs
  • Tickets 16435, 17176, 17474: Make the size of read-only fields of synced Requirements from external systems responsive to the length of their values
  • Ticket 16582: Fix the issue of submitting Defects to external defect trackers from the new TestPad
  • Ticket 16558: Fix the issue of word-wrapping of Test Step Descriptions, Expected Result and Actual Result when viewing TestPad with IE and Firefox by adding a horizontal scrollbar
  • Ticket 16598: Fix the issue of tracking execution time
  • Ticket 17142: When exporting qTest Manager data to Excel, if the original value exceeds the limit of an Excel cell, it will be trimmed
  • Ticket 17228: Allow LDAP users to log in to qTest with case-insensitive username
  • Ticket 17252: When submitting Test Log with multiple Test Steps having the same description, the system will base on the step order to set their status accordingly
  • Ticket 17072: Fix the issue of submitting Test Log with new steps
  • Ticket 17053: Fix the issue of parameters being converted back to normal text
  • Ticket 10388: The Test Case tree order will be retained when creating Test Runs with parameters
  • Ticket 10759 and 10149: You will now be able to select "More choices" in Parameters drop-down when creating Test Runs with parameters
  • Ticket 14498: a non-Project Admin user who is granted with the same permissions with the Project Admin profile is now allowed with User Management ability
  • Ticket 15162: the selected number of items per page in the TestPad will be retained for the next time you open the TestPad
  • Ticket 15909: clicking on the Jira Defect ID in "Defect Summary" grid and Statistics section will open the Jira issue page in a new browser tab or window
  • Ticket 16513: retain the custom html tags as normal text in Test Steps.
  • Ticket 16493: when link Requirements to a Test Case by selecting a Release, on Requirements under the Release scope are linked
  • Ticket 13487: You can now select recipient in an Event Notification without returning an error. This has been resolved.
  • Ticket 13459: Required fields were not functioning properly and allowing users to save without filling out the required fields. This has been resolved.
  • Ticket 14845: Ability to remove a project from a Project Group is functioning properly now. Previously, when attempting to save a Project Group after editing/removing a project from the list, the selected project would recheck itself. This has been fixed.
  • Ticket 15771: User rows in User Management are now aligned correctly if the window zoom is reduced from anything than the default 100%. Previously, if you reduced the window zoom below 100% the row aligned became skewed the further you scroll down the page. This has been resolved.
  • Tickets 15217, 15775: The export button in Test Execution>Defect Summary will now allow you to export the defects in the chosen release. This has been fixed.
  • Ticket 15467: Previously, the API /api/v3/projects/{projectId}/histories returned a '500 internal server error' when searching requirements and a '400 unsupported object type' when searching fields. This has been resolved.
  • Ticket 15431: You can now save Tests with linked bugs properly. 
  • Ticket 15507: The Configuration Label Selection screen will now retain the chosen selections after clearing the filter.
  • Ticket 15717: You can now select a color for Test Run Status when Managing Site Fields. 
  • Ticket 15442: You can now change notification settings for Defects. 
  • Ticket 16349: You will no longer receive an error when accessing previously created data queries after adding new fields to the associated element. 
  • Ticket 16320: In the Automation Test Log API, the Automation Test Run Status is now an editable attribute.
  • Tickets 16562, 16589: A Test Execution result appearing twice in the drop-down. This has been resolved.
  • Ticket 16744: qTest REST API documentation has been updated for the OAuth/login to be more clear.
  • Ticket 14961: The Jira plugin will no longer attempt to load an insecure favicon. You will not receive an 'insecure request' due to favicon from qas.qtestnet.com. This issue is fixed.
  • Ticket 16129: Previously, the Test Pad did not support formatting, and bulleted lists were written/copied in Microsoft Word and pasted into qTest. Now that the new Test Pad includes the Rich Text Editor, any test cases prior to Manager 9.1 with formatting produced from Word lost the formatting and appeared in one line of text as opposed to the desired bulleted list. This issue has been resolved and test cases entered before the release of 9.1 now include their desired formatting. 
  • Ticket 16276: When exporting a test run to Excel, lines on the test runs were not exported/formatted correctly. This issue has been resolved.
  • Ticket 16460: Formatting entered in the Preconditions field lost the desired formatting during export. This has been fixed.
  • Ticket 16464: When multiple test cases with bulleting and carriage returns were exported to Excel, the formatting was lost. This has been resolved.
  • Ticket 16400: Linebreaks using the Shift+Enter key combo have been restored. 
  • Ticket 16547: In Test Execution and attempting to view Test Runs for a Test Case, the Test Runs perpetually load. This has been resolved. 
  • Ticket 13838: The Defect status marked in Test Execution is now in sync with what is displayed in Jira, Test Execution History and the Test Execution Defects view.
  • Ticket 14371: You are now able to see a link created between a Jira Requirement and a Jira Defect. Previously, when creating a Test Case or Defect in qTest, a link is created for a Jira Requirement or Defect, but there would not be a link created from the Jira Defect to the associated Jira Requirement. This has been resolved.T
  • Ticket 16033: Test Step Description formatting has been restored for Test Cases that existed prior to the 9.1 OD upgrade.
  • Ticket 16052: The Defect record will display the Release/Build from the associated Test Run record. Previously, the 'Affected Release/Build'was not updating in the Defect record by default. This issue has been resolved.
  • Ticket 16084: The Test Execution page will no longer stick in a continual loading pattern, nor will you receive an "oops, bug error page" when attempted to mark the run as "passed" using Quick Run. This issue is fixed.

Limitation - Known Issue

  • When adding Parameters to a Test Step, if you use your mouse to select a Parameter from the drop-down, the selected Parameter is added and then the editor is switched to view mode. You will need to click the Test Step field to continue editing it.
    Workaround: If you use the arrow keys to navigate in the dropdown and the Enter key to select the Parameter, the editor will be retained.

 

Subscribe To Our Blog
Powered by Zendesk