Manager 8.5 Release Notes

June 21, 2017

Enhancements

  • Unlimited custom fields (previously limited to 20 custom fields maximum per object)

  • API Update: Added ability to paginate results from Get Test Runs API

  • Default landing page jumps to most recently visited page.

    When logging in to qTest Manager, instead of the default landing to the Test Plan page, you will be navigated to the most recent page (Most recent page for the user is defined by the most recently visited page where the user spent more than 10 seconds)

  • Deprecated syntax search. Free-text search is still available from the search bar

  • Native browser alert before page close to remind of unsaved changes

Enhanced Test Execution UI

A key highlight of qTest Manager 8.5 is an enhanced UI for Test Execution (excluding the TestPad and some pop-up dialogs). This is the first major phase of the enhanced UI for qTest Manager as a whole, which will be rolled out in phases in subsequent releases.

Test Execution Root Page

Execution Status Graph

  • The graph is located on top of the root page. It shows the overall status of Test Runs in the project

  • Hover over the graph to view percentage of Test Runs by Statuses

Execution Summary

  • The Execution Summary table shows the status of Test Runs grouped by the highest level of containers (whether that is by Releases, Cycles, or Test Suites)

  • Test Runs that are located directly under Test Execution root are grouped in “No Group”

  • This table can be exported to Excel

Test Run Assignment View

  • This grid is deprecated in the new UI. To view Test Run assignments, you can still use the Data Query or qTest Insights

Test Execution Container Pages

A container is either a Release, a Test Cycle or a Test Suite since these are groupings of Test Runs. One goal of the enhanced UI is to deliver both high-level summary and actionable details across Releases, Cycles, and Test Suites.

Statistics tab of Release, Test Cycle, and Test Suite

Execution Status Graph

  • The graph is located on top of the page. It shows the overall status of Test Runs located under the container

  • Hover over the graph to view percentage of Test Runs by Statuses

“Super-Charged” Test Run grid of Release, Test Cycle, and Test Suite

Left Navigation Panel vs Test Run Grid

  • If you click on a Release, Cycle or Suite from the left navigation panel of Test Execution, the Test Run grid will display all Test Run contents in a “flat list.” For example, if a Release is selected from the left navigation panel, the Test Run grid displays all Test Runs within that Release, regardless of whether the Test Runs are located directly within the Release or sub-contained in other Cycles and/or Test Suites within that Release

  • To view linked Defects of a Test Run, click on the number in the Defects column

Test Run Grid Pagination

  • If there are more than 50 Test Runs, the grid is paginated. You can move through pages or change the total number of items in one page up to 200 using the navigator at the top left or bottom left of the grid

Test Run Grid views specific to the user

  • The Test Run grid can be customized by each user to add, remove, and rearrange columns. This custom view will not impact other users in the project

  • The Test Run grid view will be retained, so that the user can see the same columns displayed when viewing pages for the same container type. In other words, the user has the ability to customize the view for all Test Suites, a different view for all Cycles, and another view for all Releases within the same project (without impact to other users)

Customize Columns in Test Run Grid View

  • To add/remove columns, click the Gear button and select the columns from the dropdown. A few examples of helpful columns to display:

    • Custom Fields of Test Runs

    • Custom Fields of Test Cases

    • Requirements

  • To rearrange columns, hover over the column header. Then drag the dotted handle icon to move it to the preferred position

  • Columns that must be displayed by default: ID, Name, Logs, Defects

Sort test runs in Test Run grid

  • To sort the rows by any column, click on the column header. The order of Test Runs after sort affects the user only.

  • After you sort, If you click on a different page within Test Execution, the sort will revert back to the default behavior:

    • Test Runs in a Test Suite page will be default sorted by # (Test Run order within suite)

    • Test Runs in a Release or Cycle page will be default sorted by ID (Test Run ID)

  • After you sort, If you click on a different module (such as Test Design or Requirements) and return back to Test Execution, the sort will be retained

Selecting Test Runs in Test Run Grid

  • To select individual Test Runs from the grid, select the check boxes in the first column next to the Test Runs

  • To quickly select all Test Runs, use these options from the Checkbox dropdown in the grid header:

    • Select all results: to select all Test Runs within the selected container (including Test Runs that are displayed in subsequent pages)

    • Select all on current page: to select all Test Runs currently displayed on the page

    • None: to clear the selection

  • (If you click directly on the check box, you will select all Test Runs on the current page)

Action Buttons from the Test Run Grid

  • Quick Run

  • Run

    • Select Test Runs from the grid and click on the Run button to execute based on the default execution mode (TestPad only)

    • You can also select Test Runs from the grid and click on the other execution options from the Run dropdown (which will Launch the execution and also save that default execution mode for the next time you click on the Run button:

      • TestPad only

      • TestPad + Desktop Explorer

      • TestPad + Web Explorer

  • Add Test Run(s)

    • Click Add to create new Test Runs directly under the container (Release, Cycle, or Test Suite) that is selected from the left navigation panel

  • Delete Test Run(s)

    • In addition to the right-click selection from the left navigation panel, you can also delete Test Runs from the grid using the Delete button

  • Export Test Run reports from the grid

    • In addition to the Export Test Run Reports button from the left navigation panel’s toolbar, you can also export these reports for the selected Test Runs from the Test Run grid

    • To export selected Test Run from the grid, select one of the options from the Export drop-down

      • Test Run Details: to export the selected Test Runs with the selected columns from the grid, in addition, to test step details to Excel

      • Test Execution and Defects: to export for the selected Test Run(s) to Excel. The columns in this report are the same found in the report from the left navigation toolbar

      • Test Execution and Defects - No Cell Merging: to export for the selected Test Run(s) to Excel. The columns in this report are the same found in the report from the left navigation toolbar

      • Automation Test Runs: to export selected Automation Test Run to TestNG XML file

Drag / Drop to reorder Test Runs in a Test Suite

  • In a Test Suite page, you are able to drag and drop the table rows to change Test Run order. This function is disabled in the Release and Test Cycle page

Cut or Copy Test Runs

  • This actions are still possible as a right-click option from the left navigation of Test Execution and not possible from the Test Run grid

Other tabs of Release, Test Cycle, and Test Suite

For easy access you can find other contents related to the selected Release, Cycle or Suite in these sections:

  • Properties (Properties of the Release are read-only as they’re only editable in the Test Plan module)

  • Defect Summary

  • Execution Summary (not available in Test Suite page)

  • History (not available in Release page since its Properties are not editable in Test Execution)

Test Run page

  • Click on the Run button to execute based on the default execution mode (TestPad only)

  • You can also click on the other execution options from the Run dropdown (which will Launch the execution and also save that default execution mode for the next time you click on the Run button:

    • TestPad only

    • TestPad + Desktop Explorer

    • TestPad + Web Explorer

Test Run Properties

  • This section can be collapsed and expanded to view all properties of the Test Run

  • Gray fields are in read-only mode and cannot be edited

  • Remember to click Save after you modify any properties

Execution History tab

  • List of all previous executions (Test Logs) of the Test Run

  • Test Log grid can be customized for additional columns

  • Click on a Test Log to view the details of its executed test steps

  • To link Defects to an existing Test Log or Test Step Log, click on the number in the Defects column to open the Link Defects dialog

Attachments

  • Lists all attachments in the associated Test Case (from Test Design)

  • (Attachments from the Test Log are displayed in the Test Log Details for the corresponding Test Log instead of the attachments tab)

Other tabs on Test Run page

  • Test Case Details: To view the associated Test Case properties and Test Steps. These grayed-out fields are read-only and can only be edited on the Test Case page

  • Defects: all Defects which linked to all executed Test Logs and Steps

  • Requirements: all Requirements which are covered by the Test Run

  • Sessions: all Sessions which are associated with the Test Run

  • History: changes made on the Test Run

  • Comments

Known Issues - Limitations

  • Test Run order in the grids is not consistent with the order on the Test Execution tree

  • Test Case Properties section in Test Run page: Test Case custom fields always display the latest values, regardless of the Test Run's associated Test Case version

  • Customized view of Test Run grid:

    • Only these fields are inline-editable: Name, Assigned To, Planned Start Date, Planned End Date

    • For Test Runs created from shared Test Cases: except for Test Case name and ID, other Test Case information is not displayed in the grid

Bug Fixes

  • 9170 - Notification Emails being sent to inactive qTest accounts

  • 6789 - Issue with searching imported Jira issue by ID in qTest Manager

  • 9197 - Test Run Schedules with a long title causing errors

  • 9237 - Incorrect information in Clone Project notification email

  • 8868 - Fail to execute Test Runs with Automation Integration v2