Manager 9.9.1 Release Notes

February 19, 2020

We are happy to announce qTest Manager 9.9.1 OnPremise. This release has many exciting updates, including several Feature Requests submitted by customers!

Here are a few release highlights:

  • new Rally Integration fields

  • API enhancements to create Test Cases and Test Runs with Parameters in the Test Case Steps

  • additional VersionOne Integration field

  • prevent the approval of Test Cases with no linked Requirements

API Enhancements

We have enhanced the Manager APIs 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 APIs 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 APIs

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.

  • Randomized: To 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.

  • Manual: To 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.

  • Dataset: To 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.

{
  "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.

Enhancements

Ability to Prevent the Approval of Test Cases Without Linked Requirements

Project Admins can now prevent users from approving Test Cases that do not include linked Requirements. This features enablement is on a per-project basis, and applies to the approval of newly created Test Cases, or when modifying properties or Test Steps of existing Test Cases via the UI or API.

By default, this new feature is OFF, but Project Admins can enable it from the Project Settings>Test Case Settings page.

If enabled, ensure your Project Users have the following permissions:

  • Edit Test Cases

  • View Requirements

  • Approve Test Cases

Once enabled, users must link Requirements to the below scenarios of Test Cases before approval:

  • newly created Test Cases

  • modified Test Steps of an existing Test Cases

  • modified Properties of an existing Test Case

Enablement of this feature applies to the following:

  • Approval of single Test Cases via UI

  • Batch Approve

When users Batch Approve Test Cases that have no linked Requirements, qTest confirms the Test Case versions and they can only select MAJOR versions of Test Cases to execute.

APIs:

Exceptional Users Permission

Project Admins can designate "exceptional users" who can approve Test Cases without linked Requirements even when this feature is enabled. This is managed within the Test Case Settings page.

Jira Integration-New Add-Ons

We are excited to announce the release of two new Jira Server and Jira Data Center add-ons to the Atlassian Marketplace.

Add-on Versions:

  • 6.11.14

  • 8.0.4

These new add-ons support qTest 9.7.1+ OnPremise, as well as qTest OnDemand customers that are using self-signed certificates.

However, if you are using an outbound proxy for Jira you cannot use a self-signed certificate with these new add-ons, and you are required to perform additional configuration steps or the integration will break.

Read the add-on release notes for the additional configuration information that is required.

Rally Integration Enhancement

The Integration with Rally has been enhanced to display all system and custom fields from Rally that are configured within the Projects Integration Settings. Previously, the Rally fields were hard-coded. This enhancement applies to the following:

  • Defect Mapping

  • Requirement Mapping

Project Admins with the Manage Integration Settings can map the newly available fields.

Project Field now available in VersionOne Requirement Integration

The VersionOne Project field is now included as an option in the VersionOne Requirement Integration Settings. Additionally, you can configure the VersionOne Project field to organize your "Imported from VersionOne" folder using Field 1 or Field 2 of the Requirement Integration.

This organization option is then visible on the Requirements tab within qTest once you save your Integration Settings changes. This allows you to display VersionOne Project information in each Requirement that is synced to qTest Manager.

Project Admins with the ability to configure VersionOne's Integration Settings can now:

  • Select the Refresh Fields Settings button to get the latest field setting from VersionOne including the VersionOne Project field.

  • Organize imported VersionOne's requirements with the VersionOne Project field

  • Activate the VersionOne Project field to display in the "VersionOne Properties-Read Only" section of the Requirement in qTest.

Read the Retrieving Requirements from VersionOne topic for additional information on how to use the VersionOne Requirement Integration.

Tricentis Analytics User Permissions in qTest

In preparation for the future release of Tricentis Analytics OnDemand, we have included new User Group permissions associated with Tricentis Analytics. Additionally, the User APIs of GET, Update, and Invite include these new permissions.

  • TA Viewer: Users who can view reports in Tricentis Analytics.

  • TA Designer: Users who can define reports in Tricentis Analytics.

  • TA Administrator: Users who can manage data from all qTest projects in Tricentis Analytics.

Data Query with Jira fields

In response to PIR-154, the "Data Query with Jira fields" enhancement that was released with Manager 9.8 has been modified to reduce the number of database connections. The following changes are applied to the Requirement Data Query:

The "Jira ID" field has been replaced with the "External ID" field.

In the Criteria drop-down, the "Jira Issue Type" field has been replaced with the "External Object Type" field. However, users will still see “Jira Issue Type” in Customize View, Query Results grid and Export.

If there are any saved queries that used the "Jira ID" or "Jira Issue Type" fields before, they will be changed automatically without any effect on the query result. The user will also see "External ID" and "External Object Type" in Customize View, Query Results grid, and Export.

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

Bug Fixes and Improvements

Jira Integration Update

To provide backward compatibility with Jira server versions older than 7.6, a new configurable property is introduced:

integration.jira.testConnection.legacyEndpoint.clients=<CLIENT_ID1>,<CLIENT_ID2>

This property will either be null or contain Client IDs separated by a comma, for clients who are using Jira server versions older than 7.6.

When testing the Jira connection, if the current client id matches with the values contained in this property, it will send a request to the old endpoint: /mypermissions

Otherwise, it uses new endpoint: /permissionscheme

API Update

In response to the below Module API security fix #35067, we have updated the following APIs which enhances security to view/retrieve responses from Projects and requires users to have appropriate Project level-permissions.

Therefore, from 9.8.8 and going forward, users will require Project-level permissions for any API and UI actions unless the API is specifically at the Site-level and does not target a specific Project.

  1. Module:

    • Get Modules: /api/v3/projects/projectId/modules

    • Get a Module: qtestUrl/api/v3/projects/projectId/modules/moduleId

      • Permission: Requirement and Test Design Tree

  2. Test Execution:

    • qtestUrl/api/v3/projects/projectId/test-runs/execution-statuses

      • Permission: View Test Run

  3. Link Objects:

    • Remove link objects - Success with link between build and requirements

    • qtestUrl/api/v3/projects/projectId/builds/newBuildId1/link?type=requirements

      Permission Notes:

      • Build: support requirement

        • Permission: Edit Release\Build + View Requirements

      • Release: support requirement

        • Permission: Edit Release/Build + View Requirements

      • Requirement: support Test Case

        • Permission: Edit Requirement + View Test Cases

      • Test Logs: support Defects

        • Permission: Edit Test Run

      • Test Step Logs: Defects

        • Permission: Edit Test Run

  4. Custom fields:

    • Get fields: /api/v3/projects/projectId/settings/{objectType}/fields

      • Create custom field: ( release / build / requirement / test case / test suite / test run / defect/api/v3/projects/projectId/settings/objectType/fields

      • Update system field: /api/v3/projects/projectId/settings/defects/system-fields/6421

        • Permission: Manage Field Settings

Additionally, the Automation Integration APIs listed below will also be affected with this change and users will need "Automation Schedules" Project-level permissions for the associated {projectId}:

  1. Create an Automation Agent

    • POST /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents

  2. Update an Automation Agent

    • PUT /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}

  3. Delete an Automation Agent

    • DEL /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}

  4. Activate an Automation Agent

    • POST/api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/activate

  5. Deactivate an Automation Agent

    • POST /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/deactivate

  6. Update a Job’s Status

    • PUT /api/v3/projects/{projectId}/automation/jobs/{job_id}/status

Test Step Attachments

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

Ticket # Component Description
34857 API integration

When using the API to add a new release type using Fix Versions for a Jira Integration, users were getting an error. This has been fixed.
34870 Jira Integration Atlassian API changes affected the Jira integration and some users could not create new defects from qTest to Jira nor could they save the Jira connection. Error messages were received when saving the connection "Connection failed. Permissions queries data is required". Issue types linked to Jira were not visible from the Integration Settings page. This is resolved. 
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.
34442 Notifications When saving a notification for Requirement changes, some users reported receiving an oops error. This is now fixed.
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. 
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.

The Chrome extension includes an "active tab" permission. When users click to submit a new defect to Rally, then a new browser tab/window will be open with the defect submission form of Rally. While the new tab/window is quickly loading with the auto-fill, users should not open or switch to another tab/window, or else the autofill will fail. 
33555, 33895, 34459, 34460 Test Design

Users use Ctrl+B or the Bold button to bold sections of text in Test Design. Turning bold off caused text to be added to the left of the cursor instead of the right of the cursor. This has been fixed.
33562

Test Design

Users were unable to see the bottom of the page in Chrome on a second monitor when scrolling up and down. This has been fixed.
33720 Test Design

When using the Ctrl+S hot key to save data in Test Design, some users but experienced an error that would wipe the data instead of saving. This has been fixed.
33880 Test Design

When users exported Test Cases from Excel, the format changed and added an extra line between rows. This has been fixed.
34803 Test Design

Users were experience issues where Text Copy/Paste is greyed out when in Editor mode in the Test Steps. This has been fixed.
33090 Test Execution When attempting to view a Test Cycle that included over 100,000 Test Runs, some users experienced longer than expected load times of the Test Execution page. This is now fixed.
NA Test Execution When creating a Test Run with historical parameters, users were receiving a 400 bad request error. This has been fixed.
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.
34569 Test Design

Users were experiencing issues using the Chrome spellcheck extension within Test Design. This has been fixed.
NA Security

Default web server 500 error page leaked version information. This is now resolved.
35067 Security: APIs

Previously, when using the Module API, some users were able to view/retrieve responses from Projects without appropriate permissions. This is now resolved.

The following message is the expected result: "User needs to be assigned to project to perform this action!"
35838 Docker Deployment Previously, the Docker deployment would fail the first time users attempted to download and deploy qtest and qtestlb. This is now resolved.
NA Docker Deployment The maxPostSize of TomCat in Docker is now set to unlimited.
NA qtestctl Deployment Customers now add -offline to every command to force qtestctl to run in offline mode.