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