Tosca Tests

Figure: Create TOSCA Test Case, push test case to VERA for ALM, route for approval and Approve
In Tosca, develop the Test Case using best practices for the project and your organization. This will be the most time-consuming set of activities – getting the script running correctly, following standards, handling errors, reporting checkpoints clearly, having it able to run repeatedly, etc.
Once a Tosca Test Case is developed and working correctly, it is ready to be reviewed and approved. In Tosca, set its TestCaseWorkState field to "COMPLETED".

A Test must be approved in VERA before it can run in a Test Set/Execution List.

Once a Test is Routing for Approval, the Tosca Test Case is updated so that it can no longer be modified in Tosca.
If a Test needs to be updated, use the VERA "Go" button to perform a "Revise" operation to set the Test back to a "Draft" status. Once set back to "Draft", the Tosca Test Case is updated to allow edits. Note that the default VERA role enabled to perform a "Revise" operation is "Test Manager". Your configuration may have a different role allowed to "Revise" a Test. See the VERA documentation for additional information about the "Revise" operation.

Deprecated Functionality

Tosca Tests should no longer be uploaded from the ALM Test Script Viewer tab. This method is deprecated and will be removed in a future release. All Tosca tests should now be loaded into ALM using the Tosca Add On upload feature.