qTest integration connection settings
To get started with qTest integration, first create a qTest connection, if you haven't already.
qTest example
| Field | Data |
|---|---|
|
Name |
Name of qTest server |
|
Server |
|
|
Service Account |
qTest Service account for Vera connection |
|
Service Password |
qTest Service account password |
|
Browser |
|
|
API |
|
|
qTest Name |
|
Note that qTest Name field is specific to qTest connections only.
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: qTest-Vera-RMP-sample.json is a sample Records Management file with qTest record types.