Now we will modify the Vera polices to support new business rules.

Sample Business Rules

We will configure Vera to support the following chart.

Sample Requirement: Manual and automated test case approval is based on Type and Regulation (A = Approver) below.

Vera Analysis & Design

Based on the above requirement we will need to make the following modifications:

• Update qTest Test Cases fields and field values in qTest Project.

  • Update Test Case Type field value

  • Add Regulation custom field and add field values

• Update the qTest Test Case Record Type data fields in the Records Management Policy in Tutorial Policy Set

• Modify the Approval Policy in the Tutorial Policy Set

  • Add new Approval Groups

  • Add and modify Approval Templates

The new business rules apply to the qTest Test Case and Automated Test Case Record Types. We will need to update the Approval Policy with the following Approval Templates:

qTest Project Configuration

First we will look at qTest project Field Settings for Test Case.

1. We need to update the Test Case Type Combo box list values by adding:

   1. Data Migration

   2. Configuration

   3. System

   4. Acceptance

      

2. We need to add a new Test Case custom field Regulation Combo box and add the following list values:

   1. None

   2. SOX

   3. GxP

   4. SOX & GxP

      

Vera Configuration

Now that you evaluated the business rules and updated qTest, you can update the Records Management Policy and the Approval Policy.

Records Management Policy updates

We are going to update the Records Management Policy from Add Test Run Records to Records Management Policy . Open VeraRMPTutorial-part2.json in an editor for modification.

1. 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.

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

   {
     "Records Management Policy": {
       "Version": "1.0.0.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"
             }
           ]
         }
       ]
     }
   }

2. Save the Records Management Policy as VeraRMPTutorial-part3.json

Now we have a Records Management Policy configured for the new Test Case business rules. The completed JSON file with qTest Test Case update can be downloaded:

Approval Policy updates

We are going to update the Approval Policy from Add Approval Template to Approval Policy. Open VeraAPTutorial-part1.json in an editor for modification.

First you will update Approval Roles, then you will add the Approval Templates in Rank order to make it easier to manage and troubleshoot.

Approval Roles

There are new Approval Roles you need to add to the Approval Policy: Data Owner, Product Team Member and Product Lead.

Approval Templates

Data Migration Test Case

Approval Template configuration

GxP Configuration Test Case

GxP System Test Case

GxP Acceptance Test Case

SOX Test Case

SOX & GxP Test Case

Configuration Test Case

System Test Case

Acceptance Test Case

General