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": "<service account name>",
"Service Password": "<encrypted Password>",
"Urls": {
"Browser": "https://<server address>/rest/toscacommander/",
"API": "https://<server address>/rest/toscacommander/"
},
"Auth Mode": "clientCredentials"
}
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 |
|---|---|
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 here to download a sample file.