Policy file configurations

To create qTest and Tosca connections, please see Connections management for more information.

Connections settings

qTest example

Field	Data
System	qTest
Name	<name of qTest server>
Server	https:<server name>.qtest net/"
Service Account	"<emailtesting@domain.com>",
Service Password	"<encrypted password>",
Browser	"<https://<server> name>/p/{Project ID}/portal/project#key={Key}",
API	"<https://<server> name>/api/v3/projects/{Project ID}/{Item Type}s/{Entity ID}" },
qTest Name	"<server Name>" }

Note: qTest Name field is specific to qTest connections only.

Tosca example

Field	Data
System	Tosca
Name	Tosca Server
Server	https://<server name>.<domain>.com
Service Account	<client id>
Service Password	<client secret>
Browser	https://<server address>/rest/toscacommander/
API	https://<server address>/rest/toscacommander/
Auth Mode	clientCredentials

Note: Auth Mode is specific to Tosca connection only.

HTTPS

If you are using HTTPS for the Tosca server, then you are required to provide a Client ID and Client Secret for the Tosca Synchronization user and to set the Auth Mode to clientCredentials. This user must be a member for the Locking Group for qTest entities in Tosca. The Group must also be created using the User Administration service available in the Tosca Gateway.

Note that the service account must be created with Tosca Server User Administration and the project needs to be configured for server login. The service account should be added to the Locking Group. For example: ALM_Lock.

HTTP

If you are using HTTP for the Tosca Server, then you can provide either a username and password or a client id and secret. Only set the Auth Mode property above to clientCredentials when using a client id and secret. The user must be a part of the Locking Group being used to qTest.

Note that the service account must be created in Tosca Commander Project and added to Locking Group. For example: ALM_Lock.

Records Management Policy changes

The Records Management Policy should be updated to reflect the desired fields that will be displayed in Vera. At minimum, it should contain definitions for the following:

Integration option	Required type definitions
Pre-execution Approval for Manual Test Cases	qTest Test Case, qTest Test Step
Post-Execution Approval for Manual Test Runs	qTest Test Run, qTest Test Log, qTest Step Log
Pre-execution Approval for Tosca Test Cases	qTest Test Case, qTest Test Step, Tosca Test Case, Tosca Test Step, Tosca Test Step Value, Tosca Test Step Sub Value
Post-execution Approval for Automated Test Runs	qTest Test Case, qTest Test Step, Tosca Test Case, Tosca Test Step, Tosca Test Step Value, Tosca Test Step Sub Value, qTest Test Run, qTest Test Log, qTest Step Log, Tosca Execution List, Tosca Execution Log, Tosca Test Step Log, and Tosca Test Step Value Log.

Example: Download a sample file.