Release Date

12-OCT-2023

High Level Description

1.7.0.0 release of Tosca Adapter

Notes

The Tosca Adapter was updated to include support for Tosca 2023.1.1.

Tx3 Internal Ref ID

f4de3af

Component

Version

VERA Policy Configurations:

Synchronization Policy: 1.7.0.0

Custom Toolbar Scripts

Tosca Interface Button Script: 1.7.0.0

VERA Tosca Windows Client

VERA Tosca Windows Client: R1.7.1

VERA Utilities

VERA Password Encryption Utility:  1.0.0.0

Category

Reference ID

Name / Description

Enhancement Request

VF-1410

Tosca Adapter CI Client support for Tosca 2023.1.1

IN ORDER TO provide support for Tosca 2023.1.1 CI execution through the Tosca Adapter

WE WILL update the Tosca Adapter to include the CI Client files for Tosca 2023.1.1

Category

Reference ID

Name / Description

Enhancement Request

VF-1399

Utilize the updated Trusted Publishers certificate for Tosca Adapter code-signing and import

IN ORDER TO update the Tosca Adapter code to the latest Tricentis GmbH certificate

WE WILL utilize the current Tricentis GmbH certificate to sign the Tosca Adapter code and installers

Enhancement Request

VF-1085

Pull RMP processing into library that can be reused by Tosca Adapter and Tosca Add-on

In order to use the RMP in the Tosca Adapter and the Tosca Add-On and avoid having this done in multiple places, we should pull the RMP processing code into a re-usable library so that it can be used by VERA, the Tosca Adapter and the Tosca Add-On.

Bug

VF-1050

VP & Req fields not populating correctly for Tosca Test in ALM

The issue has to do with a Tosca Test pulled into ALM via the Test Script tab (not via Tosca Add On). We have 3 scenarios for you where it works one way (correctly) in Merck’s current Production Environment, but appears to work incorrectly in Merck’s Test Env where we are testing ALM VERA / Tosca Integration & Tosca 14.

Enhancement Request

VF-1034

Create TOSCA Test Run and populate fields with Project Parameters

IN ORDER TO create a TOSCA Test Run field with values defined in VERA for ALM project parameters

WE WILL provide the ability to use project parameters in the RMP

Enhancement Request

VF-1033

Create a TOSCA Test Set and populate fields with Project Parameters

IN ORDER TO create a TOSCA Test Set field with values defined in VERA for ALM project parameters

WE WILL provide the ability to use project parameters in the RMP

Enhancement Request

VF-1030

Create TOSCA Test and populate fields from RMP

IN ORDER TO populate TOSCA Test fields with values defined in RMP

WE WILL provide the ability to use project parameters in the RMP

Enhancement Request

VF-1029

Write the name of the pdf report to the comment field of the run

IN ORDER TO write the name of the pdf report to the comment field of the run

WE WILL update the comment field to include the name of the PDF

Enhancement Request

VF-1028

Add run ids to the PDF report attachment description field

IN ORDER TO populate/display/add run ids to the PDF report attachment description field 

WE WILL update the description field on the report attachment to include the run IDs and display test instance name that were generated for the TOSCA execution of the selected test instances. 

Enhancement Request

VF-994

TOSCA Error Handling: TOSCA REST Service not available

REST API services are not responding mentioning error code 502 so that it gets cleared the reason is REST services are down.

Enhancement Request

VF-993

TOSCA Adapter Error Handling: TOSCA workspace is locked by user

Tosca workspace is locked by the user id for the requested execution list. 

Bug

VF-978

Can't Run Tosca tests on Citrix / ToscaALMClientInstaller.msi installs files on %LOCALAPPDATA%

Installer needs to install files in program data folder. The Tosca adapter needs to be able to read the program data folder. 

Bug

VF-798
VF-1379

Tosca run fields related to Test are not updated correctly (Test: Category field)

Test related fields such as "Test: Category" should be populated with the test values when the Tosca run is generated.  The test field value is currently populated from the Synchronization Policy when the run is generated but should be populated from the test field value.

Enhancement Request

VF-987

Create a Tosca Adapter installer to support Tosca version 14

The Tosca 14 CI Client files are included in the installer.

Bug Report

VF-1003

TOSCA Execution list consists of leading/trailing spaces

The Tosca nodepath attribute will be used to find the test event associated with the execution list for distributed execution.

Bug Report

VF-988

TOSCA Runs ended in "Error" are not reported in ALM VERA

The test set test instance execution status will be set to “Failed” and the Tosca execution report will be attached to

the test set indicating the error finding the screenshot directory.  The new run will be created with an execution status of “Failed”.

Bug Report

5

Set CI timeout value to 36000000 in Tosca Integration CI Client Configuration File

The Tosca Integration CI Client Configuration File is updated to set CI timeout value to 36000000 ms to allow long running tests to complete successfully.

Bug Report

4

Support Tosca 13 new test event properties for associated configuration elements

The new test event properties for configuration element association introduced by Tosca 13 are added as standard properties when generating the CI execution configuration file.

Bug Report

3

Cannot Synchronize Multiple Tosca Test Cases Simultaneously

The synchronization of test cases has been updated to correctly process the generated test cases when version control is enabled.

Bug Report

2

Tosca Test Synchronization Error with Version Control

If version control is enabled, the test case being synchronized is confirmed to be checked out properly before changes are posted.

Bug Report

1

Rest Call error due to congestion of API calls from different account on Tosca server

The service account credentials will used for the REST API calls to complete the synchronization once the selection tree is built using the user's credentials and the test case(s) or execution list(s) are selected.

Summary

Description

QC/ALM Tosca Integration - Smart Delete of Tosca test case or test set doesn't work with VERA

For the non-Admin user, Smart Delete of Tosca test case and test set doesn't work with VERA. If a user tries to delete a test or test set from ALM it will not delete the entity in Tosca. An Admin must perform this kind of operation.

QC/ALM Tosca Integration - Smart Copy/Smart Paste doesn't work for Tosca test case or Tosca test set

The Smart Copy/Smart Paste action doesn't work for Tosca test case or Tosca test set.

Smart Copy/Paste is blocked for individual Tosca type entity but if a user selects the folder and trys to smart/paste the test or test set, it will not work. An Admin must perform this kind of operation.

QC/ALM Tosca Integration - Tosca properties are editable in edit state

Tosca Properties are currently editable, until an item is routing for approval or approved. Administrative procedures and training must be in place to ensure that ALM related properties for managing links are not updated.

QC/ALM Tosca Integration - Tosca admin must perform the Tosca copy operation on item in Approval Cycle

In Tosca, if a Copy operation is needed on an item in the Approval cycle, an Admin user is required to perform the operation and also do the following:

·      Reset the status to PLANNING

·      Clear the VeraSyncId field

·      Clear the corresponding ALM id field, ALMTestID, or ALMTestSetID

This is necessary because the Tosca Copy operation also copies this data which is invalid for a new item.

Instead, it is recommended to create a new object (e.g. Execution List or Test Case), then copy the *contents* of the old item and copy the contents to the new item. This way, no Admin intervention is necessary.

QC/ALM Tosca Integration - System disruption, Mid execution leaves no results in Tosca execution log

For Execution Lists that have multiple Test Cases, running on a Tosca Agent: If some Test Cases execute and then a System Error occurs (e.g. Network, Agent failure, machine problem), then no results are logged in Tosca.

In this case, the ALM Integration creates no runs and displays a message, accordingly.

QC/ALM Tosca Integration - Imported Execution Lists may not work

When importing Tosca Execution Lists into a new Tosca repository, embedded Test Case unique ID's will not exist in the target repository and will not execute. A work around is to either manually recreate the Execution List creating the correct Tosca links to the Test Cases in the target repository, or edit the imported Execution List to correct the missing IDs.

An execution list that has been imported with these missing Test Case ID's will not associate properly with a VERA Test Set.

QC/ALM Tosca Integration - Execution Results reporting occurs at test set level

Currently, Execution Results are collected and report on, at the Test Set level. Individual Run entities, under a Test Instance, do not have Step results. Tricentis will investigate/evaluate this limitation.

QC/ALM Tosca Integration - Multiple window sessions on Tosca agents cause unpredictable behavior

If a Tosca Agent has > 1 Windows Session that had ToscaDistributionAgent.exe running, this causes unpredictable behavior. Before running official tests, make sure that only 1 Windows session is running on all potential Agents and that Remote Tests successfully execute via DEX in Tosca, before running from ALM.

NOTE: when working on an Agent machine, before logging off, manually 'Stop and Exit' the ToscaDistributionAgent.exe (from the System Tray). Then, be sure to *log off* the Windows session - do not just disconnect from the RDP connection.

QC/ALM Tosca Integration - ALM not closes the COM surrogate processes on workstation

In error situations, ALM is not closing "COM Surrogate" processes. This can cause problems on ALM Workstations, until those processes are closed. If troubleshooting, close all COM Surrogate processes via Windows Task Manager.

QC/ALM Tosca Integration - Tosca Remote Agent machine must have an active window session running

Each Tosca Remote Agent machine must have an active Windows session. The following must be true:

·      Tosca Commander must be installed on the machine, with Workspaces defined that are able to run intended ExecutionLists.

·      The session must be running ToscaDistributionAgent.exe

·      The windows user must have access to a valid Tosca License. If using Cloud, access at least once during configuration, via Tosca's License Manager App.

·      First time browser questions must be asked/answered before running any tests, for each Windows account that is active.

·      ToscaRemoteAgent must be configured correctly to invoke the correct Commander Workspace.

·      Before, running tests, you can choose the correct Workspace, as necessary

·      A dedicated "execution user" is recommended for Agent Commander sessions. For example, "ALMExecutor". That user must be able to run in the chosen Workspace

·      The ToscaRemoteAgent icon, in the system tray, must be green to indicate "Idle" and connected to the Tosca Server.

·      The RemoteAgent does not currently run as a Windows Service, therefore, there must be a running Windows session.

·      Tosca can be configured to use its "RDP Server" to unlock a locked Windows Session.

QC/ALM Tosca Integration - Tosca 'Take Screen Shot' statement must use common file share path as 'Directory' parameter value

Due to Tosca's implementation for the Take Screenshot' command, combined with Tosca's distributed architecture for large, multiuser organizations, the statement must use a common file share specification for its "Directory" parameter.

For example, "\\ToscaImageServer\Images".

Otherwise, images appear as blank boxes in Execution Reports, attached to the Test Set.

QC/ALM Tosca Integration - Tosca test cases can be added to manual test sets

The Tosca test cases currently can be added to manual test sets. There is no check for test set designer to validate if test case is manual or Tosca. As a workaround we have added that Tosca test cases cannot be executed in manual test sets so that if a test set designer will add the Tosca test case by mistake to manual test set than ALM run button and Tosca Interface Run Test Set button will be disabled for Tosca test case.