Tosca Integration Troubleshooting

Final approval from Vera fails

The following error is displayed in qTest on the record where the final approval failed.

This error happens when Vera cannot change the Tosca record to COMPLETED via the Tosca Rest API.

Some common reasons for this error are:

• The Service Account being used in the Tosca Connection settings in Vera is not a member of the locking group selected when the Tosca entity was routed for approval.

• The Rest API is not configured to use the Execution Approval settings.

Resolution:

• Ensure the user that is configured in the Tosca Connection is in the correct locking groups.

• Follow the setup instructions here: Tosca Integration - Tosca Settings | Enable Pre execution Approval Add In

Error: can’t request approval

Open

Some common reasons for this error are:

• Request Approval was selected after linking a test to qTest, not before

• Checkin did not occur prior to Requesting Approval

• In the case of multiple test case selection, one or more test cases have uncommitted changes

Resolution: For selected test(s), ensure that all local changes have been checked in to the common repository prior to the Request Approval action AND that the workflow order (Request Approval, Link to qTest, Checkin) is followed in that exact order. Also, consider performing an Update All prior to a Request Approval action to ensure that a test is in the correct status.

Error: can’t find this user group

Open

As the error message states, passwords in Tosca are based on an exact match. Refer to the suggestions in the error message for resolving mismatched passwords. In addition to the items mentioned in the message, this error can occur when an existing, but invalid user group is selected as a lock group. Only use lock groups that are authorized by your organization.

Copying test cases

Tosca test cases in IN_WORK or COMPLETED status cannot be copied and pasted, either in the same folder or into other folders. Plan ahead. If planning to make multiple copies of a test case, do so prior to the Request Approval action. Or consider using a test sheet and template. QTV supports approval of template instances. Also, note that while test cases cannot be copied in certain statuses, the tests steps can be copied. A new test case can be created, then the steps needed can be copied from one test to another.

Checkin All when closing a workspace

When working in a common repository, it common and practical to ensure all items are checked in when they are not actively being edited. Given that, when a user closes a workspace, they are prompted to check in their local items to the common repository. Use caution when this option is employed in conjunction with the integration. Checkin All is the final step in the Request Approval process, so for any tests where a Request Approval action has taken place, but changes are still pending, those changes will be committed, and the test will be locked for editing. Consider a common process where the Request Approval action is only done immediately before routing for approval and only when all changes are complete.

qTest Linkages

The integration is designed to utilize existing qTest linkage functionality, which allows for both linking and unlinking from qTest. However, when using the VERA integration, unlinking of records from qTest is not supported. Once a record is routed for approval, it should not be unlinked from qTest.

Artifacts subject to approval

Pre-execution approval is designed for test cases only. Test case related objects, such as modules, templates, and reusable test step blocks are not included in the approval process. When making changes to existing artifacts that are not subject to approval, care should be taken that the updates do not impact test focus. Change to test focus should flow through the approval process, using the Revise functionality.