The following changes need to be made in Tosca to enable Vera Integration:
This is the recommended setup using https. If your organization does not wish to use https, please contact Tricentis support.
Create Project using Tosca Server
Create a new project for the workspace
Open the Tricentis Tosca Server page in the web browser. This is configurable, but the default is http://localhost.
Navigate to the Admin Console and login with Admin credentials.
3. Click the Add Project button and fill in the appropriate information for Project Details. Test connection to confirm it is valid and save.
4. The project will now appear in the list of projects in Project Overview.
Create Service Account User
Create a service account for Vera to access Tosca Commander
From the Tricentis Tosca Server page in the web browser, navigate to User Administration. Reauthenticate, if needed, using Admin credentials.
2. Navigate to the Users tab and click Invite users
3. Enter the email address that will be used by the service account. This will be used as the username in Tosca Commander. Click the Add button.
4. Specify a name for the service account. Note that this name will be displayed in Tricentis Server based Administration only. As mentioned above, the username shown in Tosca Commander will be automatically set to the service account email address.
Add Locking Group
Create a group used to lock Tosca Test Cases
Navigate to the groups tab within User Administration. Click the Create Group button.
2. Click the Create group button and provide a name and optional description for the lock group. We recommend using ALM_Lock. Click Create.
Server based user administration will allow two groups to have the same name. Avoid naming the lock group the same as a local group or creating a local user group with the same name as the lock group. This can break the process of requesting approval from Tosca.
3. The new group will now be shown in the list of user groups
Add Service Account to Locking Group
Add the service account to the Locking group
Click on the tile for the newly created lock group and once inside the group summary, select edit.
2. In the next window, select service account checkbox and click the assign button. Save changes.
3. The service account will now be a member of the lock group.
The service account should be the only member of the lock group! Do not add other users to this group as it will bypass the controls in place for the approval process.
Associate the group to the project
Navigate to Project Administration. The project that was created will be shown in the list of projects. Navigate to the project details page by selecting the Details icon.
2. In Project Details, click on the “+” (plus) icon to open the Select Groups window. Check the box next to the lock group that was created and click the Assign Groups button.
3. After assigning groups, the Save button will be enabled. Click Save.
4. The Lock group will now appear in the list of groups for the project.
Create the Workspace
Open Tosca Commander and click on the button Create New to create a new workspace
In the Create New Workspace window, select Tricentis Server Repository as the type of repository and click the button to log in to Tricentis Server.
3. In the next window, enter Admin login credentials
4. After authenticating, enter workspace information. Select the appropriate project from the Project name dropdown and select a name for the local workspace. Click OK.
5. Once inside the new workspace, navigate to the Usermanagement tab and checkout the project root.
6. While focused on the project root, right click and select Sync Users from Tosca Server from the context menu.
7. After the sync is completed, the lock group will be present in the list of groups and the service account will be a member of this group.
Note that there are two groups named Admin. This is expected and necessary for usermanagement to function properly.
Enable Dokusnapper
If you wish to view Tosca run reports in VERA, you must enable the Dokusnapper functionality in Tosca; the setting is disabled by default.
In Tosca Commander, navigate to Settings → TBox → Dokusnapper.
Set the value of Enable Snapper to Yes and the Storage Location Type to Tosca.
Both of these settings must be configured exactly as shown above. When Dokusnapper is enabled, but the Storage Location Type is Local, only a local copy of the test run report will be saved. VERA will not be able to retrieve a copy of the Dokusnapper report from the database and therefore the report will not appear in the VERA record.
3. Perform a Checkin All to save the changes to the common repository.
Enable Send Test Case Work State to qTest
In order to synchronize the test case workstate between Tosca and qTest, you must enable Tosca to send test case workstate to qTest.
Navigate to Settings → Commander → General → Advanced.
Right-click on the folder Advanced, and select Create… → Setting
3. In the new Setting, enter the name and value:
Name: SendTestCaseWorkStateToQTest
Value: True
4. Close Settings and perform a Checkin All to save the changes to the common repository.
Enable Pre-execution Approval Add-In
Enable the AddIn in Tosca Commander (client-side)
The following setting needs to be added to C:\Program Files (x86)\Tricentis\Tosca Testsuite\ToscaCommander\ToscaCommander.exe.config
<configuration>
<configSections>
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</sectionGroup>
</configSections>
<applicationSettings>
<Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings>
<setting name="ExecutionApprovalEnabled" serializeAs="String">
<value>True</value>
</setting>
</Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings>
</applicationSettings>
</configuration>
2. Enable the AddIn in the Rest API
The following setting need to be added to C:\Program Files (x86)\Tricentis\Tosca Server\RestApiService\TCAPIRestServiceStandalone.exe.config:
<configuration>
<configSections>
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</sectionGroup>
</configSections>
<applicationSettings>
<Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings>
<setting name="ExecutionApprovalEnabled" serializeAs="String">
<value>True</value>
</setting>
</Tricentis.TCAddIns.ExecutionApprovalAddIn.Properties.Settings>
</applicationSettings>
</configuration>
Enable Pre-execution Approval
EnableExecutionApproval from the Tosca workspace
From within the Tosca workspace, checkout the project root
Right click and select Enable execution approval from the context menu
3. Pre-execution approval is now enabled. Tosca Commander will display a message once the feature has been enabled.
