Tosca Integration - Policy File Configurations

Synchronization Policy Changes

The Synchronization policy must be updated to reflect connection information for qTest and Tosca.

qTest example

{
  "System": "qTest",
  "Name": "Staging Server",
  "Server": "https://<servername>.qtestnet.com",
  "Service Account": "administratoremail@domain.com",
  "Service Password": "<encrypted Password>",
  "Urls": {
     "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>"
}

Tosca example

{
   "System": "Tosca",
   "Name": "Tosca Server",
   "Server": "https://<server name>.<domain>.com",
   "Service Account": "<client id>",
   "Service Password": "<encrypted client secret>",
   "Urls": {
       "Browser": "https://<server address>/rest/toscacommander/",
       "API": "https://<server address>/rest/toscacommander/"
    },
    "Auth Mode": "clientCredentials"
 }

Using 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: 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 (example: ALM_Lock)

Using 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: The service account must be created in Tosca Commander Project and added to Locking Group (example. ALM_Lock)

Record 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

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.

Click on this link to download a sample file.