Add Test Run Records to Records Management Policy

Now that you created a Records Management Policy and added Test Case records, we can add Test Runs following the same approach. In this tutorial, we will only create one test run record type for qTest. We will add a new Record Type to VeraRMPTutorial-part1.json.

In the example below we are only showing the qTest Test Run record due to the size of the file.

Create qTest Test Run Record Type

  1. Add a Record Type Name. We are going to start by defining a qTest Test Run. We will create a unique test run record type for qTest and Tosca tests:

    { "Revision": "2", "Records Management Policy": { "Version": "Vera Tutorial 2", "Schema": { "ID": "http://tx3services.com/schemas/0/0/records-management-policy.json", "Major": "0", "Minor": "0" }, "Record Types": [ { "Name": "qTest Test Run" } ] } }
  2. Define the Record Type by System and Item Type. qTest is the System and the Item Type is test-run:

    "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:

    { "Revision": "2", "Records Management Policy": { "Version": "Vera Tutorial 2", "Schema": { "ID": "http://tx3services.com/schemas/0/0/records-management-policy.json", "Major": "0", "Minor": "0" }, "Record Types": [ { "Name": "qTest Test Run", "Definitions": [ { "Systems": ["qTest"], "Item Types": ["test-run"], "Singular Name": "Test Run", "Plural Name": "Test Runs" } ] } ] } }
  3. 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:

    Here is the updated Records Management Policy with above code block:

  4. 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 the Fields section to the Record Type. Add the Status, Test Case ID, Test Case Version, Target Release/Build, and Execution Type:

    Here is the updated Records Management Policy with above code block:

Create qTest Test Log Record Type

  1. qTest Test Runs have a sub-record type: Test Log. Add the qTest Test Log as a record type as well. Start by adding the Record Type Name under Record Types:

    Here is the updated Records Management Policy with above code block:

  2. Add the qTest Test log definition with the System qTest and Item Type test-log:

    Here is the updated Records Management Policy with above code block:

  3. Add the record fields you want to include in Vera by adding the Fields section to the Record Type. Add the Test Case Name, Test Case ID, Test Case Version, Status, Tester, Target Release/Build, Execution Type, Executed Start, Executed End, and Execution Log Notes:

    Here is the updated Records Management Policy with above code block:

Create qTest Test Step Log Record Type

  1. qTest Test Logs have a sub-record type: Test Step Log. Add the qTest Test Step Log as a record type as well. Start by adding the Record Type Name under Record Types:

    Here is the updated Records Management Policy with above code block:

  2. Add the qTest Test Step definition with the System qTest and Item Type test-step-log:

    Here is the updated Records Management Policy with above code block:

  3. Add the record fields you want to include in Vera by adding the Fields section to the Record Type. Add the Status, Description, Expected Result, Actual Result, Executed, and Tester:

    Here is the updated Records Management Policy with above code block:

Now we have a Records Management Policy configured for qTest integration. The completed JSON file with qTest Test Case, Automated Test Case, and qTest Test Runs can be downloaded here:

Next we will create Approval Routes for the records defined in the Records Management Policy, Add Approval Template to Approval Policy