Manager 10.4 Release Notes

May 10, 2021

Vera post-execution approval

With the Vera 2021.2 release, Post Execution Approval for Automation Test Runs has been added to the Vera integration configuration page. When the Vera integration is on and the Post Execution Approval for Automation Test Runs check box is selected, users who select an Automation Test Run or Tosca Test Run will see the following optional Vera fields:

• Vera ID

• Vera Approval Status:

  • Draft (default), Routing, Rejected, Approved

• Vera Pending Tasks

• Vera Approval Route

• Vera Rejection Reason

Using the qTest APIs to update Automation Test Runs and including Vera fields in the request will prompt qTest to validate the Vera field values and update the Vera fields.

DEX with AOS now supported for Tosca integration

When integrating Tricentis Tosca with Tricentis qTest, you can now use Tosca Distributed Execution (DEX) with AOS. For more information on integrating Tosca with qTest, refer to qTest and Tosca Integration: Quick Start Guide.

Legacy Reports tab deprecation

The legacy Reports tab has been removed, as well as the permission setting related to Reports. All data that was available via the Reports tab are available within qTest by running a data query within Manager, reporting within Insights, or utilizing our Tech Preview of Tricentis Analytics to accomplish your reporting needs.

Tricentis Analytics permissions and groups

The User Groups permissions for the application process of Tricentis Analytics have been removed from qTest Manager. User Access to Tricentis Analytics Tech Preview is now handled within the developer portal. Instructions for getting started with Tricentis Analytics Tech Preview can be found here.

ForceAuthN config for SSO

A new setting has been added to the SSO configuration page so that an Admin can enable or disable the ForceAuthN parameter configuration by choice. The configuration is enabled by default, so users are forced to re-authenticate if their sessions are not expired.

Active Directory integration improvements

qTest's Active Directory/LDAP integration now supports LDAP groups. Admins can now directly integrate AD groups within qTest, further simplifying user permissions configurations tied to them.

For more information on LDAP configuration, go to Add and Modify LDAP Connections. For more information on importing LDAP users and groups, go to Importing LDAP Users and Groups.

Single Sign On log in update

With our ongoing effort to simplify the user experience, we now have streamlined the log in experience for SSO users. The qTest Native Login Credentials are now available as a link directly below the SSO Log In button.

Admins have control over log in interactions for users, including requiring Identity provider and inactivity timeout control.

Test Execution page

The Test Execution page now allows better visibility to Defects when using the Vera integration. After routing a Test Run for Vera Approval, the Defect icon will be displayed next to the Test Log/Test Step to indicate any Defects linked to it. Clicking on the Defects icon will open a dialog with the list of linked Defects. Users will NOT be able to create/link Defects in the dialog at this time.

Test Steps - Additional Information

Two new data points are now available to enable better audits:

• Date & Time Stamp

• Tester Name

For example, if a Tester executes a Test Run manually and applies the execution status to the individual Test Steps, the timestamp and the user who performed the action will be captured and displayed.

The two new data columns, Executed and Tester, will also be available in TestPad. These will display the timestamp and the user when a user clicks to change the status of a Test Step. This will not be applied to the Quick Run feature.

The following APIs have been updated to include the above changes:

• Submit Auto Test Log

• Submit Manual Test Log

• Modify Auto Test Log

• Modify Manual Test Log

• Batch Submit Test Log 1

• Batch Submit Test Logs 2

The optional property "exe_date" has been added to "test_step_logs" so that users can input timestamps. The new property will be returned in the response if the Test Log is created successfully.

Sample Request: { "status": {"id": 601}, "exe_start_date": "2021-03-25T04:22:00.436Z", "exe_end_date": "2021-03-26T04:22:00.436Z", "test_step_logs": [ { "test_step_id": 6136, "status": {"id": 603 } }, { "test_step_id": 6137, "status": { "id": 601 }, "exe_date": "2021-03-26T04:21:00.437Z" } ] }

Sample Response:

The following GET APIs have also been updated with the optional "exe_date" and "tester" properties for "test_step_log":

• Get Test Logs

• Get a Test Log of a Test Run

• Get Last Run Log

API enhancements

API enhancement to include external Jira issues

We have enhanced the GetRequirement API and the search API to allow for the addition of external Requirement issue ids. This will allow customers to build dashboards that show Jira story link information which expands usability of these dashboards by non-qTest users. The following APIs have been enhanced:

• Gets multiple Requirements

• Gets a Requirement

• Queries objects

We have added an optional parameter for these APIs:

• include_external_properties

Sample Request: New OPTIONAL parameter: "include_external_properties" Values: true/false Default value: false Only affects when _object_type = requirements

Sample Response: qTest requirements "external_properties": { "id": "", "link": "", "uniqueid":"" } External requirement (JIRA, V1...) "external_properties": { "id": "JIRAP-4575", "link": "https://jira.usaa.com/browse/jirap-4575", "uniqueid": "12345" }

New APIs to create and update custom site fields

Tricentis has expanded our support for custom site fields with new APIs. The new APIs allow users to create and update new Site fields, as well as update custom fields at the Project level.

New APIs for custom Site fields

Create custom Site field

This new API allows users to create custom Site fields.

• POST <site URL>/api/v3/fields/{objectType}

Sample Request: { "label": "Name", "required": true, "constrained": false, //only applicable for checkbox, combo box, multi selection combo box "order": 1, "allowed_values": [ //only applicable for checkbox, combo box, multi selection combo box { "value": 601, "label": "Passed", "order": 1, "is_default": true, "is_active": true, } ], "multiple": false, "data_type": 1, "searchable": true, //not applicable for type = Date picker, Date Time picker, User list "default_value": "string", //applicable for all types except: checkbox, combo box, multi selection combo box "original_name": "Name", }

Required attributes: field's name field's type "is_active" is not applicable for Site field.

Update custom Site field

This new API allows users to update custom Site fields.

• PUT <site URL>/api/v3/fields/{objectType}/{fieldid}

Sample Request: { "instanceType": "NumberDataType", "id": 1, //not applicable when creating new field "label": "Name", "required": true, "constrained": false, //only applicable for checkbox, combo box, multi selection combo box "allowed_values": [ //only applicable for checkbox, combo box, multi selection combo box { "value": 601, "label": "Passed", "order": 1, "is_default": true, "is_active": true, "color": "#c0c0c0" // not applicable for any custom field type } ], "multiple": false, "data_type": 1, //can't be changed "searchable": true, //not applicable for type = Date picker, Date Time picker, User list "default_value": "string", //applicable for all types except: checkbox, combo box, multi selection combo box "system_field": true, //not necessary "original_name": "Name", //not applicable when updating field }

Depending on the data_type, the user is allowed to update different fields: Type data_type Fields allowing updates Text box 1 name, searchable, required, default value, field's order Text area 2 name, searchable, required, default value, field's order Rich text editor 6 name, searchable, required, default value, field's order Number 7 name, searchable, required, default value, field's order URL 12 name, searchable, required, default value, field's order Combo box 3 name, searchable, required, list of values (default value, active/inactive, value's order), field's order Check box 8 name, searchable, required, list of values (default value, active/inactive, value's order), field's order Multiple selection combobox 17 name, searchable, required, list of values (default value, active/inactive, value's order), field's order User list 5 name, required, default value, field's order Date picker 4 name, required, default value, field's order Date time picker 9 name, required, default value, field's order

Delete Site field

This API allows users to delete a custom field at the Site level.

• DELETE <site URL>/api/v3/fields/{objectType}/{fieldid}

Get a Site field

This new API allows users to get info for a specific Site field providing its ID.

• GET <site URL>/api/v3/fields/{objectType}/{fieldid}

Get all Site fields per object type

This new API allows users to get a list of all Site fields per object type.

• GET <site URL>/api/v3/fields/{objectType}

The list of results can be paginated. Users can use the following parameters to define pagination:

• page (Optional): By default the first page is returned if this field is omitted

• pageSize (Optional): By default, the number of objects in each page is 100 if this is omitted. Users can specify a custom number (up to 999) in this parameter

New APIs for custom Project fields

Update Project custom fields

This new API allows users to update a Project's custom field. Users will not be able to change the field type, but they will be able to update the following: field's name, active/inactive field, field's value, value order, mark default value, field is searchable, and required field.

• PUT <site URL>/api/v3/projects/{projectId}/settings/{objectType}/fields/{fieldID}

Sample Request: { "label": "Name", "required": true, "constrained": false, //only applicable for checkbox, combo box, multi selection combo box "allowed_values": [ //only applicable for checkbox, combo box, multi selection combo box, user list { "value": 601, "label": "Passed", "order": 1, "is_default": true, "is_active": true, } ], "data_type": 1, //can't be changed "searchable": true, //not applicable for type = Date picker, Date Time picker, User list "default_value": "string", //applicable for all types except: checkbox, combo box, multi selection combo box "is_active": true }

Depending on the data_type, the user is allowed to update different fields: Type data_type Fields allowing updates Text box 1 name, searchable, required, default value, field's order Text area 2 name, searchable, required, default value, field's order Rich text editor 6 name, searchable, required, default value, field's order Number 7 name, searchable, required, default value, field's order URL 12 name, searchable, required, default value, field's order Combo box 3 name, searchable, required, list of values (default value, active/inactive, value's order), field's order Check box 8 name, searchable, required, list of values (default value, active/inactive, value's order), field's order Multiple selection combobox 17 name, searchable, required, list of values (default value, active/inactive, value's order), field's order User list 5 name, required, default value, field's order Date picker 4 name, required, default value, field's order Date time picker 9 name, required, default value, field's order

Delete custom Project field

This new API allows users to delete a Project's custom field.

• DELETE <site URL>/api/v3/projects/{projectId}/settings/{objectType}/fields/{fieldID}

Get a custom Project field

This API allows users to get info for a specific Project's custom field providing its ID.

• GET <site URL>/api/v3/projects/{projectId}/settings/{objectType}/fields/{fieldID}

Exclude allowed_values

qTest supports thousands of values per Site Field. To improve performance around Fields, we have made changes to the exclude allowed_values from APIs related to Site Field.

• API to get all Site field per object type

• API to get Site field by ID

• API to create/update field

New link for requesting new features

The Suggest New Feature option in the Help menu has been renamed to Request New Feature. In addition, this option now directs you to the new Tricentis Idea portal, allowing you to more easily request features and suggest improvements for qTest.

Bug fixes

Ticket #	Component	Description
N/A	Security Updates	qTest's security has been updated to remove potential vulnerability issues for customers.
INC0287795	Jira, Rally, and VersionOne Integrations	Updated confirmation message with more details: Deleting an Integration Connection - "Deleting this connection will also delete external linked Defects and convert external linked Requirements and Releases to Internal Requirements and Release. Are you sure you want to delete this connection?" Deleting a Requirement mapping inside an Integration Connection - "Deleting this mapping will also convert corresponding external linked Requirements to internal Requirements. Are you sure you want to continue?"
INC0240930	API	Users experienced errors when using the Search API. After opening a new defect, but closing before saving, the unsaved defect was reported in the Search count. This has been fixed.
INC0296607	Data Query	Users experienced errors when creating a Test Case Query that contained a combination of Requirement Fields and Test Case Fields. This has been fixed.
INC0297993	Jira Integration	A parsing error for the value of the Parent Link Field in Jira has been fixed.
INC0272134	Test Run	Users were unable to send the Test Run notification email if the event template contained a variable of linked Requirements. This has been fixed.