Tricentis Tosca

Introduction

ConnectALL now supports the syncing of records from the Tricentis Tosca server to other applications. You can choose the option "Tricentis Tosca" as illustrated in the below image to configure an app-link.


Supported Authentication

  • HTTP Basic

Supported Entity Types

  • Requirements
  • RequirementSet
  • Issues
  • TestCaseFolder
  • TestCase
  • ExecutionList
  • ExecutionList Folder
  • Execution Entry
  • Execution Test Case Log

Supported Functionalities

  • Sync Fields
  • Sync Attachments
  • Sync Parent-Child linking

Attachments Feature

  • Create
  • Update

Application Link Configuration in ConnectALL

Configuration of Application Server

You will need the below details to create the application in the Tosca application server.  

  • URL (Add the URL of the Tosca commander installed location)
  • Username
  • Password

Note: If you are using ConnectALL version 2.10.4 or higher, you will be able to enter the Tosca workspace details in the configuration screen (right side image) itself.

Tosca Configuration screen

Tosca Configuration screen (for version 2.10.4 and above)

Entity Mapping

The Tosca adapter requires a special mapping of the parentID to create and update entities as shown in the below image.  The parent ID is a unique ID for one particular record or an entity, such as a ‘Requirement set’, and it has a designated unique ID.  The below screenshots display mapping in various scenarios.

Field Mapping Type-Issue

The defect type is an entity that plays a main role in issue creation. ConnectALL will not synchronize any records for that entity(issue) If this is not configured. Further, create a value mapping to map the ‘Defect type’ as shown in the below images, If you are creating an applink for an issue type (entity).

Tip

Starting from the version 2.10.23, a new field, ‘ExecutionListId’ will be available in the field mapping screen for Tosca. This is especially useful when you have an app-link between Tosca’s ExecutionTestCaseLog and MicroFocus ALM’s Test Run entities. In that scenario, you could create a mapping between Tosca’s Execution ListId field and Microfocus ALM’s Cycle ID field.

Tip

If you are mapping MicroFocus ALM with Tricentis Tosca, starting from version 2.10.24, you could map ALM’s Test Folder to Tosca’s TestCase Folder and sync the test steps under them.

Setting up Time Difference Calculation

You can easily define the time difference calculation in ConnectALL when you are configuring an application link.  This is essential for syncing your records with the correct time difference.  To set the time difference,

  1. Go to Entity Mapping
  2. Click to expand the Advanced Properties option (below image).
  3. Enter the required information in the Time Difference.

Time Difference Configuration

To know how to calculate the time difference, and configure it in the ConnectALL UI,  read the topic Time Difference Configuration.

Parent-Child Linking

ConnectALL supports ‘Parent-Child’ linking for Tosca.  To enable ‘Parent-Child’ linking, create a parent-child hierarchy in the Tosca server association hierarchy.  For example, let’s assume that the ‘Requirement Set’ folder is set as the parent and the ‘Requirement’ is set as the child under that.  In such a scenario,

  • Create two app-links in ConnectALL- one for the parent, and one for the child.
  • You can create a link with the parent "Requirement set", and a link with the child 'Requirement'(This is one of the types of entities).

ConnectALL then syncs the parent and the child as you have created the links.  The below screenshots display the mapping.

Parent Link Mapping:

Child Link Mapping:

Poll Query

ConnectALL supports poll query for Tosca to selectively fetch records from the server. The poll query syntax is given below:

Unsupported Fields

  • Comments
  • Attachment as URL

Troubleshooting

When using a Tosca record in an app-link, you may face a couple of issues that may require you to implement certain workarounds. We have discussed below, the issues, the scenarios leading to those issues, and the workarounds that you can implement. 

Issue 1 – Synchronization Failure

Scenario: A ConnectALL app-link is trying to synchronize a Tosca record but that Tosca record is open in the Tosca commander. As a result, the synchronization fails. 

This problem primarily occurs because Tosca Commander locks a project when it is open, and hence synchronization attempts for that project will fail. So, you cannot trigger a synchronization of the app-link when the project that you have used in an app-link is open in the Tosca Commander.

To get around this issue, ensure that the project in the app-link remains closed in the Tosca Commander when you are triggering a synchronization in ConnectALL. In other words, ensure that none of the users have the Tosca project open in the Tosca commander when the synchronization is being triggered.

Issue 2 – Unable to open a Tosca project in the Tosca Commander

Scenario: You are unable to open a Tosca project (in the Tosca Commander) when the app-link (in ConnectALL) is attempting to synchronize a Tosca record in that same project.

You will not be able to open a Tosca project (in the Tosca Commander) when the same record is a part of the app-link that is being synchronized. This is because ConnectALL locks the project/record when it is being processed, and you will not be able to open the same project in Tosca Commander. 

One way to work around this issue is to temporarily disable the app-link in ConnectALL.  This releases the lock on the specific record. As the lock is released, you will be able to open the project. 

Workaround

Closing the project in Tosca Commander to enable synchronization, or disabling an app-link to open a project in Tosca may become a time-consuming ordeal.

One way to work around these issues is to schedule synchronization outside of working hours, or perhaps at a certain well-known time of day, such as at lunch-time. Let all users know the synchronization schedule ask them to ensure they do not have the project locked at that time.

Here is another suggested workaround:
Create two projects in Tosca Commander with a shared folder structure (say, Project1 and Project2). In short, you will be cloning a project. In the ConnectALL app-link, use ‘Project1’ (this project will be used when the synchronization is attempted). If you have to verify the project or change any details in ‘Project1, open ‘Project2’ in the Tosca Commander, and make the necessary changes and ‘Project1’ will be updated as they are both cloned.