Manager 9.1.1+ Release Notes

9.1.9 Release Notes

July 25, 2018

Improvements and Bug Fixes

• Ticket 12289: Rally Defect Status is now displaying correctly in the Defect Summary page as well as Insights.

• Ticket 17804: Test Step formatting will now export as expected.

• Ticket 18217: The History for a Requirement or Test Case will no longer produce an error message when you try to review the History after making an update.

• Ticket 18185: The 'All Test Runs Query' will now show all data as expected.

• Ticket 18243: The 'Defect Query" will now show all data as expected.

• Ticket 18286: The "Mark all Selected Steps" functionality will now work correctly when continuing execution for a previously saved Test Run.

• Ticket 18356: The Test Execution Filter criteria will now filter properly.

• Ticket 18346: Test Steps will no longer produce a 'spinning' icon after collapsing a Test Step section and attempting to expand the Test Step section again.

• Ticket 18405: Data Query results will now display Custom Field values properly.

9.1.8 Release Notes

July 9, 2018

Improvements and Bug Fixes

• The color black has been removed and replaced with dark slate gray from the 'Test Run Status' color pad because the status label could not be read if a user selected black.

• You can now add a value up to 59.9 for the 'Planned Time' field when using a data query to batch edit Test Runs. Previously, you could not enter a value higher than 2.99. This issue has been resolved.

• Test Cases can now be copied from one project to another without resulting in an error. This issue has been resolved.

• The Edit message will now display properly when a requirement associated with a test case is edited. This has been fixed.

• qTest API - Project - 500-Internal Server Error with SQL query is returned in JSON response when sending request "Gets all Users in a Project" with inactive=false. THis has been fixed.

• You can now update a Test Run from a shared test case via API.

• The Configurations section in Site Administration will now require the Display Name value to be entered before you can save. Previously, you could save a new Configuration without a display name value entered, which would result in an error.

9.1.7 Release Notes

June 21, 2018

Improvements and Bug Fixes

• Unable to move on to creating new Test Runs for a test case that has parameters when creating multiple runs. Resolved.

• If multi-selected, it would like to be changed to display the selection target instead of 'Multiple Selection' in the UI. Resolved.

• Execution Type Field.Resolved.

• Deleting of custom fields. Resolved.

• Can not move forward to cell using TAB key in Firefox, IE11. Resolved.

• A user is unable to combine sorting and check-box selection in the add-project-users window. Resolved.

• Unable to tab through test steps. Resolved.

• API - Send API update TestRun to change to previous test case version, but status in tree changed to Unexecuted. Resolved.

• Not validate for input data when assign a value to parameters in creating Test Run. Resolved.

9.1.6 Release Notes

June 12, 2018

Improvements and Bug Fixes

• Question about selecting data rows vs specifying range of rows. Resolved.

• Drag/Drop/Move Permissions To Relocate Requirements for QA Role. Resolved.

• Field Settings, default value is not shown when preview. Resolved.

• Defect API - Manager 8.7.3 not supported with Tasktop. Resolved.

• API Token for Integration with Jenkins is getting outdated. Resolved.

• SSO - Question about resetting password option with SSO. Resolved.

• Swagger Docs - Marking required paramters in POST bodies. Resolved.

• Defects Section. Resolved.

• Can not create Test Run from test case which contains parameters. Resolved.

• Saving fail error when user update Assign To field for requirement, test suite, defect in case artifact has a combo box type site/custom field with empty value. Resolved.

9.1.5 Release Notes

June 1, 2018

Enhancements

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, three 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

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" check box.

6. Save and then select the Fetch Jira Defect button. Refer to Configure Jira Defects 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.

APIs with Shared Test Cases Modified

The following APIs 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 APIs:

• 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

• Ticket 13951: After assigning selected users to projects, the selection (check box) 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

9.1.4 Release Notes

May 9, 2018

Improvements and Bug Fixes

• 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

9.1.3 Release Notes

April 27, 2018

Enhancement

Test Pad Time Tracking Updates

Time Tracking in the Test Pad has been updated to display the actual execution time in the Time Tracking tab if the Time Tracking setting is enabled to automatically calculate your execution time. This way the execution time is synchronized from the time tracking auto-calculation to what is displayed in the Time Tracking tab (which was previously only for manual time tracking entries before Manager 9.0.)

Improvements and Bug Fixes

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

9.1.2 Release Notes

April 19, 2018

Improvements and Bug Fixes

• Ticket 14961: The Jira plug-in 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.

9.1.1 Release Notes

April 13, 2018

Enhancements

Firefox Integration Browser Plug-in

You are now able to install and use the Firefox Integration Browser Plug-in that is accessible from the Resources page. This plug-in 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 APIs

  • GET/POST /api/v3/projects/{projectId}/releases

  • PUT /api/v3/projects/{projectId}/releases/{releaseId}

  • GET /api/v3/projects/{projectId}/releases/{releaseId}

• Build APIs

  • GET/POST /api/v3/projects/{projectId}/builds

  • PUT /api/v3/projects/{projectId}/builds/{buildId}

  • GET /api/v3/projects/{projectId}/builds/{buildId}

• Test Cycle APIs

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

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

  • GET/POST /api/v3/projects/{projectId}/requirements

  • PUT /api/v3/projects/{projectId}/requirements/{requirementId}

  • GET /api/v3/projects/{projectId}/releases/{requirementId}

• Test Case APIs

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

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

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

Improvements and Bug Fixes

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