Menu

qTest Manager 9.8.2 + OnDemand Release Notes

Manager 9.8.7 November 21, 2019

Bug Fixes and Improvements

Ticket #  Component  Description
NA Test Execution When creating a Test Run with historical parameters, users were receiving a 400 bad request error. This has been fixed.

Manager 9.8.6 November 18, 2019

Bug Fixes and Improvements

Ticket #  Component  Description

33087

Rally integration When submitting Defects to Rally, the autofill function was not working. After the Defect was submitted successfully, users were not redirected to qTest. This is now resolved.
33562, 33659, 34461, 34144 Test Design In full-screen mode on a second monitor via the Chrome browser, users who scrolled up and down multiple times in the Test Design screen were unable to see the bottom of the screen. This is fixed.

Manager 9.8.5 November 7, 2019

Enhancement

Ability to Display the Password for Project Integration Connections

Project Admins now have the ability to view the password/token that is associated with integrated Projects. This enhancement is associated with an upcoming release for qTest Scenario, where the password/token is needed. A "Show Password" checkbox has been added to the Add Connection dialogue and is not selected by default. Once selected, Project Admins can view and copy/paste the password or token.  When closing the Add Connection dialogue, the checkbox resets to the default and the password/token will be hidden again.

This enhancement is available for the following integration connections:

  • JIRA
  • VersionOne
  • Rally
  • Bugzilla
  • Fogbugz
    show_password_alm_connection.png

Bug Fixes and Improvements

Ticket #  Component  Description

30481

Licenses page On the Administration>Licenses page, the License Information section displays the date the qTest License is due to Expire. Previously, the field was labeled as "Expired On," which was past tense. We have updated the field name to "Expires On" for future tense grammatical representation.

33813

Test Execution After adding Test Cases from the ADD button in the Test Execution Tab, users needed to refresh the page in order to select the Test Cases to edit them. This is now resolved.

34442

Notifications When saving a notification for Requirement changes, some users reported receiving an oops error. This is now fixed.

Manager 9.8.4-1 October 30, 2019

Bug Fixes and Improvements

Ticket #  Component  Description

34361

Pulse Access Users were unable to access Pulse from the 9-box due to a change in the access token used for authentication to the app. This is now resolved. 

Manager 9.8.4 October 29, 2019

API Enhancements

We have enhanced the Manager API's to allow our users to create Test Cases and Test Runs with Parameters in the Test Case Steps. 

Test Case APIs

Create a Test Case : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when creating a Test Case.

  • Parameters will be automatically added to the current Project.
  • The provided parameter_identifier must exist in the Parameters application to work.
  • The allowed input uses the [~<parameter_identifier>] format.
  • Potential Error message: return code of 404 with list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Update a Test Case : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when updating a Test Case.

  • Parameters will be automatically added to the current Project.
  • The provided parameter_identifier must exist in the Parameters application to work.
  • The allowed input uses the [~<parameter_identifier>] format.
  • Potential Error message: return code of 404 with list of all invalid parameters. Ex: "parameter1, parameter2 not found"

You can use the following GET Test Case API's to get Test Cases that contain Parameters in the Test Step’s description.

Test Step APIs

Create a Test Step : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when creating a Test Step.

  • Parameters will be automatically added to the current Project.
  • The provided parameter_identifier must exist in the Parameters application to work.
  • The allowed input uses the [~<parameter_identifier>] format.
  • Potential Error message: return code of 404 with a list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Update a Test Step : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when updating a Test Step.

  • Parameters will be automatically added to the current Project.
  • The provided parameter_identifier must exist in the Parameters application to work.
  • The allowed input uses the [~<parameter_identifier>] format.
  • Potential Error message: return code of 404 with a list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Test Run API's

Create a Test Run : we now support the ability to Create Test Runs via randomizing, manually and dataset via API. You can use the Gets a Batch Test Logs Submission jobs state API to track the "Create Test Runs" job.

  • RandomizedTo create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The maximum number of test runs can be created depending on the combined type.
  • ManualTo create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The maximum number of test runs that can be created is 100.
  • DatasetTo create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The number of test runs that can be created depend on number_of_rows property and it should not be more than 100.

Sample payload:

{
  "name": "Test Run Name",
  "properties": [
    {
      "field_id": 123,
      "field_value": "123"
    }
  ],
  "test_case": {
    "id": 123,
    "test_case_version_id": 111
  },
  "dataset_id": 123,
  "from_row": 10 ,
  "number_of_rows": 5
}

Update a Test Run : we now support the ability to update parameter values to an existing Test Run step. 

  • Return updated test run information with updated test case steps. Parameter values set/updated to test run.

Sample payload:

"assign_parameter_values": [
            {   "step_id": 233045404,
                "parameter_values": ["parameter_value_name"]
            },
            {   "step_id": 233045402,
                "parameter_values": ["parameter_value_name", "parameter_value_name"]
            },
            {   "step_id": 233045430,
                "parameter_values": ["parameter_value_name"]
            }
]
  • "assign_parameter_values": if the provided assign_parameter_values property AND test run is linking to a test case version AND the test run has an executed test log for this test case version then we DO NOT allow to set/update parameter values.
  • "step_id": belongs to the specified test case/test case version.
  • "parameter_values": belongs to the specified parameters in the above test case step. 

Improvement

While performing a Test Run, you can now save a new Test Step that only contains an attachment.

Manager 9.8.3 October 16, 2019

Bug Fixes and Improvements

Ticket #  Component  Description

30612

JIRA Integration When selecting the Retrieve JIRA Data button on the JIRA Integration > Requirements section, the manual sync would stall for some JIRA Server users. This is now resolved.

PIR-148

JIRA Integration The JIRA integration and qTest synchronization were not performing properly for many users. This is fixed.

33411, 33598

33406, 33407

33416

Email Notification Many users received duplicate email notifications stating they had been assigned to a Project, or assigned to a Project as an Admin, when the users were previously assigned. This issue is now resolved. 
33094 Data Query The Data Query for JIRA fields were not updating as expected. This issue was related to the data sync with JIRA integration. This is now fixed. 

 

Manager 9.8.2 October 7, 2019

Bug Fixes and Improvements

The JIRA Requirements integration was not auto-linking properly in qTest. This is now fixed. Previously, some users experienced an issue with JIRA requirements already synced to qTest, when changes were made to the Fix Version/Sprint of a User Story in JIRA.

Ticket Component Description
23921 TestPad Notes added to an execution log, displayed the qTest servers timezone instead of the timezone associated with the PC. The timestamp displayed in the note was UTC. This is now fixed.

31327, 31908

31373, 33175

32821, 

Test Execution  Exported reports for Test Execution would not display all headers for the selected columns of the "Export Test Run Detail" feature. Additionally, after exporting, some of the previously selected fields would no longer be visible for selection again. This is resolved.
32588, 33264 Test Execution  Some users encountered an issue when attempting to export Test Run Details when a custom field was removed from the Test Run. This placed a null value in the selected columns for the report, which returned an error. This is now resolved. 
33222 Notifications Previously, notification settings were not saving properly when activating/deactivating. This is now fixed.
Powered by Zendesk