...
Add Type and Regulation to the qTest Test Case Record Type in addition to the existing fields, Status, Description and Precondition. The Automated Test Case Record Type inherits fields from the qTest Test Case Record Type with
"Base Record Type": "qTest Test Case"
element.Code Block "Fields": [ { "Name": "Status", "Is Data": true }, { "Name": "Description", "Is Data": true }, { "Name": "Precondition", "Is Data": true }, { "Name": "Type", "Is Data": true }, { "Name": "Regulation", "Is Data": true } ] }
Here is the updated qTest Test Case Record Type in the Records Management Policy with above code block:
Code Block { "Revision": "3", "Records Management Policy": { "Version": "Vera Tutorial 3", "Schema": { "1.0.0.0" "ID": "http://tx3services.com/schemas/0/0/records-management-policy.json", "Major": "0", "Minor": "0" }, "Record Types": [ { "Name": "qTest Test Case", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-case"], "Singular Name": "Test Case", "Plural Name": "Test Cases" } ], "Author": { "Source": "Route Owner" }, "Constraints": [ { "Type": "Field Is Not Equal", "Name": "Automation", "Value": "Tosca" } ], "Fields": [ { "Name": "Status", "Is Data": true }, { "Name": "Description", "Is Data": true }, { "Name": "Precondition", "Is Data": true }, { "Name": "Type", "Is Data": true }, { "Name": "Regulation", "Is Data": true } ] }, { "Name": "qTest Test Step", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-step"], "Singular Name": "Test Step", "Plural Name": "Test Steps" } ], "Fields": [ { "Name": "Description", "Is Data": true }, { "Name": "Expected Result", "Is Data": true } ] }, { "Name": "Automated Test Case", "Base Record Type": "qTest Test Case", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-case"], "Singular Name": "Test Case", "Plural Name": "Test Cases" } ], "Author": { "Source": "Route Owner" }, "Constraints": [ { "Type": "Field Is Equal", "Name": "Automation", "Value": "Tosca" } ] } ] } }
Save the Records Management Policy as VeraRMPTutorial-part3.json
...
Code Block |
---|
{ "Route Templates": [ { "Name": " Acceptance Test Case", "Rank": "90", "Prevent Author Approval": false, "Record Types": [ "qTest Test Case", "Automated Test Case" ], "Constraints": [ { "Type": "Field Is Equal", "Name": "Type", "Value": "Acceptance" }, { "Type": "Field Is Not Equal", "Name": "Regulation", "Value": "GxP" }, { "Type": "Field Is Not Equal", "Name": "Regulation", "Value": "SOX" }, { "Type": "Field Is Not Equal", "Name": "Regulation", "Value": "SOX & GxP" } ], "Levels": [ { "Name": "Level 1", "Approvers": ["Business", "Business"] } ] } ] } |
Default Approval Template
Update the current Default Approval Route with the changes below:
Configuration element | Value | Code Snippet | ||
---|---|---|---|---|
Name | Default |
| ||
Rank | 100 |
| ||
Record Type | Any | Add all record types
| ||
Constraints | No Constraints | No constraints are defined
| ||
Level 1 Approvers | Product Team Member |
| ||
Prevent Author Approval | TRUE |
|
The completed Route Template for Data Migration Test case Default Route Template is below:
Code Block |
---|
{ "Route Templates": [ { "Name": "Data Migration Test Case", "Rank": "10", "Prevent Author Approval": false, "Record Types": [ "qTest Test Case", "Automated Test Case", "qTest Test Run" ], "Constraints": [], "Levels": [ { "Name": "Level 1", "Approvers": ["Product Team Member"] } ] } ] } |
...
Next let’s verify our configuration changes by importing Test Cases and Routing the Test cases for approval. First, Import the below Excel file to add Test Cases with Regulation and Type fields defined.
View file | ||
---|---|---|
|
Now that the Tests Cases are in qTest you can route each of the Test Cases for approval to verify the polices are configured correctly.
Select each imported test case and click the Route for Approval button. Reload the record and view the Vera Approval Route and compare the Approval Route with the Approval Route documented in the Test Case Step. If you configured Vera correctly the results will match.