Tosca Distributed Execution.

Distributed System

Distributed System is a collection of autonomous computer systems that are physically separated but are connected by a centralized computer network that is equipped with distributed system software. The autonomous computers will communicate among each system by sharing resources and files and performing the tasks assigned to them.

TOSCA Distributed Execution (DEX): 

Tosca's Distributed Execution speeds up test execution by remotely managing and distributing your automated test sets across multiple virtual machines, computers in your network or in the cloud.

Tosca Distributed Execution is provided for multi-user environments that use a common repository.

How DEX works: 

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. 

You create a TestEvent in Tosca Commander and check in the changes to the common repository. A TestEvent contains several ExecutionLists.

Once you press Execute now in Tosca Commander, it sends the request to the Tosca Distribution Server.

The Tosca Distribution Server distributes these ExecutionLists between the available Tosca Distribution Agents.

Once a Tosca Distribution Agent has executed an ExecutionList, the system saves the results to the common repository.

1. It is used to do parallel executions which can be executed from TOSCA Commander, qTest , Any DevOps Tools like AzureDevops , Jenkins.

2. User should create Test Events in TOSCA Commander and Link the Execution list which needs to be executed in DeX

3.Proper Configuration setup should be done in TOSCA Commander in order to Execute the Tests in Right Agent Machines

4.All the Agent Machine should be RDP enabled and Bypass Windows Start Screen to execute Keyboard and Mouse commands.

5. TOSCA server should be installed along with DeX Server in Windows Server Machine

6. ALL DeX Agent Machine should be connected with DeX Server with TOSCA server End point in Agent Configuration Setup

7. CI Server should be setup along with proper configuration in order to execute scripts from CI tools Azure DevOps or Jenkins etc.

8.Certificate should be installed in TOSCA Server for making HTTPS

Features: 

1. Runs tests in parallel across platforms - Run multiple tests and regression sets in parallel across various platforms, allowing you to accelerate your releases.

2. Unattended execution and real-time monitoring - Run UI tests on machines with locked screens via unattended execution. you can easily monitor the status of the distributed test events and see which agents are being used. 

3. Real-time monitoring - A web based event monitor shared real-time alerts on agent health during your distributed test execution, and gives you the ability to heal agents remotely.

4. Clear reporting and result collection - Gain a detailed breakdown of the test log info and step-by-step results of the test execution in tosca, allowing you to gain a full picture of your release readiness.

5. Easy configuration - Automated load balancing achieves the optimal distribution of test sets- automatically.

DEX Set up Options:

You can set up Tosca Distributed Execution in one of the Following ways : 

1. DEX with AOS (Automation Object Service)

2. DEX without AOS. 

Note - These two ways of setting up tosca DEX are mutually exclusive. You must choose one or the other. Tricents recommends setting up DEX with AOS, Since it has a number of Advantages over Distributed Execution without AOS.

1. DEX with AOS(Automation Object Service) 

To set up Distributed Execution with AOS (Automation Object Service), follow the steps below:

1. Install the Tricentis Tosca Server on the machine where you want the Tosca Distribution Server.

2. Install Tosca Commander on the following machines:

   • All machines on which you want to create TestEvents and trigger their execution.

   • The machine that holds the Tosca Distribution Server.

3. Install Tosca Distribution Agents on the machines where you want your agents, i.e. the machines that should execute the TestEvents.

4. Administer licenses for the installations of Tosca Commander and for the Tosca Distribution Agents.

5. Start your Tosca Distribution Agents.

6. For each agent, define the connection to the Tosca Distribution Server.

7. On each machine from which you want to trigger executions with Tosca Commander, define the connection to the Tosca Distribution Server.

8. Activate Distributed Execution with AOS.

9. Set up workspaces.

10. Create and configure test results folders.

Once you have set up Distributed Execution with AOS, you can perform the following actions:

• Create and execute your TestEvents.

• Monitor the execution of your TestEvents with the Tosca Distributed Execution Monitor.

NOTE - To take advantage of the performance improvements that Tosca Distributed Execution offers, install the Tosca Distribution Server and the Tosca Distribution Agents on separate machines.

Tosca Distribution Agents:

Tosca Distributed Execution works with two types of Tosca Distribution Agent:

• Execution Agent

• A full installation of Tosca Commander

Execution Agent

Use Execution Agent if you want to save memory and disk space.

This agent can only execute TestCases created with engine 3.0. You can use Execution Agent with Tosca Unattended Execution and Tosca Continuous Integration, provided that you are not running mixed and/or classic tests.

A full installation of Tosca Commander

A full installation of Tosca Commander can execute TestEvents created with Classic Engines, Engines 3.0, or both. They work with Tosca Unattended Execution and Tosca Continuous Integration.