Tosca Distributed Execution SetUp

Distributed Execution with Automation Object Service(withAOS):

1. Create tests

Tosca Distributed Execution is available for multi-user environments. This means that you and other users share a common repository, which is a database that stores test data and test results. Each user retrieves test data, modifies the data, and checks in their changes to the same repository.

You create your tests in Tosca Commander. To do so, you need a workspace that has access to the common repository. Each instance of Tosca Commander on which you want to create tests and trigger executions requires a separate workspace.

2. Trigger execution

When you trigger the execution of a TestEvent in Tosca Commander, it sends the request to the Tosca Distribution Server.

3. Retrieve test data

The server retrieves the test data from the common repository through the Automation Object Service. This service accesses the common repository through a workspace.

4. Distribute execution tasks

The TestEvent whose execution you triggered contains several ExecutionLists. The Tosca Distribution Server distributes these ExecutionLists between the available Tosca Distribution Agents.

Agents synchronize with the server on a regular basis. Once an agent contacts the server, the server hands over the first ExecutionList of the TestEvent to this agent. As soon as the next agent contacts the server, the server hands over the second ExecutionList of the TestEvent to this agent. If there are no agents available, the server queues the ExecutionList(s) until an agent becomes available.

5-6. Save test results

Once a Tosca Distribution Agent has executed an ExecutionList, it sends the results to the server which in turn saves the results to the common repository through the Automation Object Service.

You can monitor the execution of your tests and view the test results with the Distributed Execution Monitor.

Distributed Execution Monitor - The Distributed Execution Monitor is a web-based application that is part of the Tricentis Tosca Server installation.

With the Distributed Execution Monitor, you can do the following:

1. configure your agents
2. monitor and recover your agents
3. monitor the execution of TestEvents
4. cancel the execution of TestEvents

Tricentis recommends installing the Distributed Execution Monitor and the Tosca Distribution Server on the same machine.

Distributed Execution without Automation Object Service(withoutAOS)-

Distributed Execution without AOS works similarly up until the point where the Tosca Distribution Server receives the request to execute from Tosca Commander.

1. Create tests

Tosca Distributed Execution is available for multi-user environments. This means that you and other users share a common repository, which is a database that stores test data and test results. Each user retrieves test data, modifies the data, and checks in their changes to the same repository.

You create your tests in Tosca Commander. To do so, you need a workspace that has access to the common repository. Each instance of Tosca Commander on which you want to create tests and trigger executions requires a separate workspace.

2. Trigger execution

When you trigger the execution of a TestEvent in Tosca Commander, it sends the request to the Tosca Distribution Server.

3. Distribute execution tasks

The TestEvent whose execution you triggered contains several ExecutionLists. The Tosca Distribution Server distributes these ExecutionLists between the available Tosca Distribution Agents.

Agents synchronize with the server on a regular basis. Once an agent contacts the server, the server hands over the first ExecutionList of the TestEvent to this agent. As soon as the next agent contacts the server, the server hands over the second ExecutionList of the TestEvent to this agent. If there are no agents available, the server queues the ExecutionList(s) until an agent becomes available.

4. Retrieve test data

As the Tosca Distribution Server cannot access the common repository, it cannot retrieve test data. It only distributes the request to available agents. Consequently, each agent retrieves the test data from the repository directly.

5. Save test results

Once an agent has executed an ExecutionList, it saves the test results to the common repository.

To retrieve test data and save test results, each agent needs a separate workspace which has access to the common repository.

You can monitor the execution of your tests and view the test results with the Distributed Execution Monitor.

Advantages of Distributed Execution with Automation Object Service(withAOS) - 

Faster setup

Distributed Execution with AOS is easier to configure. You don't need to set up a workspace for every Tosca Distribution Agent.

Performance gain

Distributed Execution with AOS is more efficient. Tosca Distribution Agents work independently from a central repository and don't need to query a workspace for items to execute.

Better handling of multiple common repositories

Unlike Distributed Execution without AOS, agents in Distributed Execution with AOS don't have their own workspaces. The Automation Object Service is the single point of contact to the common repository, and you can set it up to work with multiple common repositories. When you switch to work on a new common repository in Tosca Commander, you do not need to switch anything manually.

Can run the same ExecutionList in parallel

In Distributed Execution without AOS, an ExecutionList can only run on one agent at any given time. So if the same ExecutionList is part of several TestEvents, then it is possible that the execution of some TestEvents cannot progress until that ExecutionList runs as part of another TestEvent.

In Distributed Execution with AOS, the same ExecutionList can run in parallel on several agents. This results in significant performance improvements.

Can specify a test results folder for each TestEvent

In Distributed Execution without AOS, you can define multiple test results folders and save the test results of each TestEvent to a different folder.

Note - Tricentis recommends using Distributed Execution with AOS. 

Distributed Execution with AOS has a number of advantages over Distributed Execution without AOS.

What are the components of TBox?

Tosca XScan:

To assist you in identifying controls in your test application, Tosca XScan provides various identification options. Tosca XScan identifies controls based on their attributes, the default identification method. If controls cannot be uniquely identified by their controls, there are additional ways to identify them.

Controls can be identified in the following ways:

• Identify controls by properties,
• Identify controls via anchor,
• Identify controls by index,
• and Identify controls via an image.

Tosca XML Engine:

Tosca XML Engine 3.0 allows you to modify, create, validate, and verify XML structures. XML elements, CDATA sections, and XML declarations can all have their properties, values, and comments guided at the same time. The Tosca XML Engine 3.0 is included in the basic installation of Tricentis Tosca.

Tosca XBrowser Engine:

Tosca XScan allows you to construct XBrowser Modules for web application testing. You'll need to install the Tosca Automation Extension for your browser to use the XBrowser Engine. Depending on your browser, you can install it immediately or manually.

Tosca Webservice Engine:

Tosca Webservice Engine 3.0 allows you to steer Web Services using HTTP (HTTP). It's possible to guide web services that use SOAP (Simple Object Access Protocol) or REST Webservices (Representational State Transfer). During the basic Tricentis Tosca installation, the Tosca Webservice Engine 3.0 is deployed automatically.

Tosca Mobile Engine:

Tosca Mobile Engine 3.0 from Tricentis allows you to automate the testing of mobile applications. TestCases can be run on various mobile platforms, devices, and applications utilizing various connection methods. The topics in this chapter cover how to set up and run tests with the Mobile Engine 3.0.

How many types of Engines available in Tosca

Tosca has two types of engines – 

1. Classic (or version 1.0) engines 

2. TBox (or version 3.0) engines

Tricentis’ TBox engine was introduced in the 7.x series and has several advantages. Tricentis has been creating more and more TBox engine modules.

Tosca has discontinuing support for Tosca’s classic engines after the planned release of Tosca 15.1 in February 2022. 

Please Check out  blog for more information: http://ow.ly/UOM750HFOeK

Types of Modules in Tosca

Tosca has two types  of Modules:

Classic Modules - Use classic engines to steer test objects.
XModules - Use XEngines which are based on the Tosca TBox Framework.

What is Index, Notations or ResultCount in Tosca

What is Self-Healing Mode in Tosca

What is Cardinality in Tosca

What are all the Standard Modules available for TDS in Tosca.

What are all the Standard Modules available for TDS in Tosca.

1. TestData - Find&provide item
2. TestData - Create & provide new item
3. TestData - Update item
4. TestData - Move item to type
5. TestData - Delete item
6. TestData - Import items
7. TestData - Export items
8. TestData - Update type
9. TestData - Expert module

What are all the Standard Modules available for EXCEL in Tosca.

What are all the Standard Modules available for EXCEL in Tosca.

1. TBox Open Excel Workbook
2. TBox Close Excel Workbook
3. TBox Define Excel Range
4. TBox Create Excel Worksheet
5. TBox Excel Range Manipulation
6. TBox Run Excel Macro
7. TBox Delete Excel Worksheet
8. TBox Update Excel Worksheet
9. TBox Clear Excel Range
10. TBox Excel 1:1 File Compare

What are all the Standard Modules available for SAP in Tosca.

What are all the Standard Modules available for SAP in Tosca.

SAP ContextMenu

SAL Login

SAP Logon

SAP Menu

SAP Multiple Logon Licence Warning

SAP Statusbar

SAP SubToolBar

SAP Toolbar

SAP TreeView

SAP Logon-               Open with Solution Manager

SAP Emulated Tree

SAP Emulated Table Tree

Classes::

  ContextMenuEntry

  MenuEntry

  TreeMenuEntry

What are all the Standard Modules available for Folder Operations in Tosca.

What are all the Standard Modules available for Folder Operations in Tosca.

1. TBox Create Folder
2. TBox Delete Folder
3. TBox Copy Folder
4. TBox Folder Existence

What are all the Standard Modules available for File Operations in Tosca.

What are all the Standard Modules available for File Operations in Tosca.

1. TBox Image Compare
2. TBox File Existence
3. TBox File Compare
4. TBox Delete File
5. TBox Copy File
6. TBox Read/Create File
7. TBox Append File
8. TBox Move/Rename File

What are all the Standard Modules available for Buffer Operations in Tosca.

What are all the Standard Modules available for Buffer Operations in Tosca.

1. TBox Name To Buffer
2. TBox Delete Buffer
3. TBox Set Buffer
4. TBox Partial Buffer

What are all the Standard Modules available for Windows Operations in Tosca Standard Modules.

What are all the Standard Modules available for Windows Operations in Tosca Standard Modules.

1. TBox Take Screenshot
2. TBox Clipbord
3. TBox Send Keys
4. TBox Window Operation
5. TBox Scroll Window Operation
6. TBox Save As
7. TBox Dialog
8. TBox Context Menu

TQL

 Tosca Query language (TQL) is one of the most underrated but powerful query language.

The TQL search is context-dependent. This means that the starting point has an effect on the search to be carried out. A search, which is performed on the basis of a project root element, produces different results from one based on the topmost Module folder.

TQL is deeply rooted in Tosca. Even the normal, Simple Search dialog is based on it.

Q.  How we would like to know if all created TestCases have been assigned to ExecutionLists.

=>SUBPARTS:TestCase[COUNT("ExecutionEntries")==0]

Q. Below query can be used to identify modules which are not linked to any test steps. This can be more useful to identify ideal module and further those can be used or deleted.

=>SUBPARTS:XModule[COUNT("TestSteps")==0]
OR
->COMPLEMENT(=>SUBPARTS:XModule,=>return SUBPARTS:XModule->TestSteps)

Q. Below query can be used to identify test cases which are not linked to any execution list and which are 3 years old. this can be used to identify scripts which are likely to be deleted due to less usages.

->INTERSECTION(->COMPLEMENT(=>SUBPARTS:TestCase,=>return SUBPARTS:TestCase->ExecutionEntries),=>SUBPARTS:TestCase[CreatedAt <= "6/29/2020 2:14:36 AM"])

Q. Below query can be used to identify test cases that don’t have reusable Test block. as per best practice your test script must have good amount of RTBS for quick maintenance (there can be few exceptions).

->COMPLEMENT(=>SUBPARTS:TestCase,=>SUBPARTS:TestStepFolderReference->TestCase))

Q. Below query can be used to identify duplicate modules (specially standard modules) with same name. this further can be used to cleanup duplicate modules.

=>SUBPARTS:XModule[Name == "OpenUrl"]

Q. Below query can be used to identify requirements that are having zero weightage.

=>SUBPARTS:Requirement[Weight==0]