Troubleshooting Tips

Owned by HB Farris
May 12, 2022
1 min read

Admins can update Tosca fields in ALM and ALM fields in Tosca.

  • Tosca Commander on the Server: always run Tosca Commander as an Administrator on the Server. Always remember to close the Workspace when done. Remember that the Integration cannot run if that project's Workspace is open with Tosca Commander on the Server. Usually, an Error 500 is returned to VERA.
  • Checkin/Checkout: if a user leaves an item checked out, an Admin can "Revoke" a checked out item.
  • On a Copied Tosca item that is to be kept and has ALM info, clear these fields:
    • Set OwningGroupName back to the "unlock" group to the project.
    • Clear ALMTestID/ALMTestSetID
    • Clear VeraSyncID
  • Reporting: make sure the Template's PrintOutputFormat setting is "AskUser"
  • Reporting: make sure there is only one report Template per Tosca repository. If there is one or more in other folders, reporting does not work after a Test Event executes.
  • Reporting: if a Report has a blank box where a screen shot should be, this usually means that the Test Step does not have the correct directory specification that points to the common share.
  • User Administration: If you change a PW for a user in Tosca, you have to perform a "RefreshAll" operation in the Server's Workspace for that project, before Tosca recognizes the change in the Integration (i.e. via REST calls).
  • Monitor: the Tosca Monitor reads information from the DEX (Distributed Execution) log. If DEX's logging level is not low enough, Integration Test Events will not show up in the Monitor screen.