Vera Integration

qTest includes the ability to integrate with Tosca and Vera, which is an e-signature tool used for validation testing within a LifeSciences FDA regulated environment. This integration allows you to route a test case linked in qTest through Vera for e-signature approval before executing the test case.

Vera integration in qTest supports the following types of approvals for the corresponding test execution objects:

• Pre-execution approval for manual test cases

• Post-execution approval for manual test runs

• Pre-execution approval for Tosca test cases

• Post-execution approval for automation test runs

• Approval for requirements

• Approval for defects

Before you start

Follow these instructions from the Vera documentation to configure Vera to connect with qTest (opens in a new tab).

Add your Vera service account as a qTest user, then add this user to the Administrators user group.

Enable Vera integration in qTest

Follow the instructions below to enable the Vera integration:

1. In the project where you want to enable the Vera Integration, select the gear Settings icon .

2. Select Integration Settings from the dropdown.

3. In the External Systems panel on the left-hand side, select the Vera tab to display the Vera integrations page.

4. Enter the following Vera URL in the Vera URL field:
   https://<YOUR VERA URL>/api/qtest/route-action

5. Select the checkbox next to each type of approval you want to implement.

6. Switch the Activation status to ON and save. Refresh your browser to view any changes.

Vera integration fields

After you enable integration, the objects you decide to use Vera with update with additional fields associated with the Vera integration.

The qTest Test Case Properties display the following Vera information:

• Vera ID: ID of the approval record.

• Vera Approval Status: Draft, Routing, Approved, Rejected
• Vera Approval Route: Displays details on the Approval Task, Status, Reviewer, Date, and Level for the all pending or completed approvals and rejections.

• Vera Rejection Reason: The cause for the rejection entered in the Reject Selected Entity dialog.

• Vera Pending Tasks: Lists the reviewers who still have a Pending status.

This Vera information that populates in the qTest Test Run Properties is available in Data Query, as well as exported reports. The qTest Test Run Properties display the following Vera information:

• Vera ID: ID of the approval record.

• Vera Approval Status: Draft, Routing, Approved, Rejected
• Vera Approval Route: Displays details on the Approval Task, Status, Reviewer, Date, and Level for the all pending or completed approvals and rejections.

• Vera Pending Tasks: Lists the reviewers who still have a Pending status.

The qTest Requirements and Defects display the following Vera information:

• Vera ID: ID of the approval record.

• Vera Approval Status: Draft, Routing, Approved, Rejected
• Vera Approval Route: Displays details on the Approval Task, Status, Reviewer, Date, and Level for the all pending or completed approvals and rejections.

• Vera Pending Tasks: Lists the reviewers who still have a Pending status.

• Vera Revision Number: This revision number is set to 1 when the objected is created, and goes up incrementally each time the it's revised.

• Vera Rejection Reason: The cause for the rejection entered in the Reject Selected Entity dialog.

What's next

Now that the integration is enabled, depending on your selections you can route the following objects to Vera for approval:

• Test cases

• Tosca test cases

• Automated and manual test runs

• Requirements

• Defects