...
Add a Record Type Name. We are going to start by defining a qTest Test Run. We will create unique Test Runs for qTest and Tosca tests.
Code Block language json { "Revision": "2", "Records Management Policy": { "Version": "Vera Tutorial "1.0.0.0"2", "Schema": { "ID": "http://tx3services.com/schemas/0/0/records-management-policy.json", "Major": "0", "Minor": "0" }, "Record Types": [ { "Name": "qTest Test Run" } ] } }
Define the Record Type by System and Item Type. qTest is the System and the Item Type is test-run
Code Block language json "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-run"], "Singular Name": "Test Run", "Plural Name": "Test Runs" } ]
Here is the updated Records Management Policy with above code block:
Code Block language json { "Records Management Policy": { "Version": "1.0.0.0", "Record Types": [ { "Name": "qTest Test Run", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-run"], "Singular Name": "Test Run", "Plural Name": "Test Runs" } ] } ] } }
Define the Record Author. The Record Author can be the Route Owner (the person who routed the record for approval) by a record field value or by the Actual Testers. Actual Testers are the people who created qTest Execution Logs and executed Execution Log Steps.
Code Block "Author": { "Source": "Actual Testers" }
Here is the updated Records Management Policy with above code block:
Code Block language json { "Records Management Policy": { "Version": "1.0.0.0", "Record Types": [ { "Name": "qTest Test Run", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-run"], "Singular Name": "Test Run", "Plural Name": "Test Runs" } ], "Author": { "Source": "Actual Testers" } } ] } }
We are not adding any Constraints to the qTest Test Run record because all qTest Test Runs will be defined as qTest Test Runs in Vera. Add the Record Fields you want to include in Vera by adding Fields to Record Type. Add the Status, Test Case ID, Test Case Version, Target Release/Build, and Execution Type.
Code Block language json "Fields": [ { "Name": "Status", "Is Data": true }, { "Name": "Test Case ID", "Is Data": true }, { "Name": "Test Case Version", "Is Data": true }, { "Name": "Target Release/Build", "Is Data": true }, { "Name": "Execution Type", "Is Data": true }
Here is the updated Records Management Policy with above code block:
Code Block language json { "Records Management Policy": { "Version": "1.0.0.0", "Record Types": [ { "Name": "qTest Test Run", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-run"], "Singular Name": "Test Run", "Plural Name": "Test Runs" } ], "Author": { "Source": "Actual Testers" }, "Fields": [ { "Name": "Status", "Is Data": true }, { "Name": "Test Case ID", "Is Data": true }, { "Name": "Test Case Version", "Is Data": true }, { "Name": "Target Release/Build", "Is Data": true }, { "Name": "Execution Type", "Is Data": true } ] } ] } }
...
Next we will create Approval Routes for the records defined in the Records Management Policy, Add Approval Routes Template to Approval Policy