Troubleshooting
It is recommended to install and use the Tosca Monitor. See the Tosca documentation for details. Note: the "Distributed Execution" logging level should be set low enough to see CIClient events – for example, set the logging level to DEBUG. The default level does not show execution request from the CIClient, and this is what the Integration uses to submit execution requests.
Try these suggestions for troubleshooting problems:
"Tosca" is not a choice in a Test's "Type" dropdown list |
The Integration components are not installed correctly. Carefully review and repeat related steps. The Server-Side ALM components must be setup correctly. Restart the ALM Service. |
When creating a Tosca Test or Test Set an error is returned. |
Try using a browser or a REST application such as Postman to try some Tosca REST calls from the ALM client machine. "http://server:port/rest/toscacommander/"- should respond with a version number. If successful, Tosca REST service is setup and running.
|
VERA operations fail – when clicking the VERA "Go" button, a Tosca/REST error displays. |
There is likely an erroneous configuration setting. Check the policy file settings. Check the Property names in the target Tosca project/repository. For example, make sure that the integration Property names on Test Cases and ExecutionLists are spelled correctly, with correct case. (e.g. ExecutionList has properties spelled "ALMTestSetID" and "VeraSyncId") |
Unauthorized error from Tosca |
Make sure the account exists and password is correct on the Tosca Server. NOTE: Tosca User ID's are case-sensitive! |