Distributed Execution Implementation
Parag Kukwas
Head of Customer Service | Partner Enablement | Author of Dr. Tosca | Global enabler
Problem
Abhishek - Dr. Tosca, How to set up Distributed execution?
Description
Last time we have discussed what is distributed execution and its type. How about the implementation? How to implement the distributed execution and what are the pre-requisites for me to set up the distributed execution?
Prescription
Dr. Tosca - Abhishek, I am glad that you have decided to implement the distributed execution in your company and asked about the prerequires. We will go through the pre-requisites for the distributed execution while implementing the same in my machine.
Pre-requisites
-?????????Tosca server 15.0
-?????????Tosca Commander 15.0
-?????????Tosca Commander 15.0
-?????????1 DB (MS SQL preferred) hosting Common repository.
-?????????As you can see all the machines both Tosca commander and one Tosca server and Database hosting server in the same network
-?????????Two workspaces connected to the same repository.
-?????????Tosca Commander and Tosca server version is the same
Terms to be known before we start let's see the common terminologies
-?????????Agent: Tosca?Distribution Agents?are the machines that execute your?TestEvents.
-?????????Test Event: A Test Event organizes the execution with?Tosca?Distributed Execution.
-?????????Configuration: Configurations specify which?Tosca?Distribution Agents?should execute which ExecutionLists within the TestEvent.
-?????????Event monitor: Tosca?Distributed Execution (DEX) Monitor?is a web-based application that allows you to monitor your?Tosca?Distributed Execution?tests and?Agents.
Disclaimer: In this setup, the Tosca commander and Tosca server are in the same machine, and the Execution agent is on a different machine. All component is present in the same Network.
Agent Machine
-?????????Install a Tosca commander or execution agent as per the license you procure.
-?????????Create a workspace if the workspace is not already present using the same connection string which will connect the workspace to the common repository.
-?????????Navigate to “C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\DistributedExecution” and run “ToscaDistributionAgent.exe” as Administrator
-?????????As soon as it started running right click on the agent from the right bottom menu and click on configure the agent. “ToscaDistributionAgent.config” window will open.
-?????????Go to the Setup workspace tab and provide the path of workspace which you have created for distributed execution along with the Username and password to login to the workspace.
-?????????Go to the “Connect to server” tab and provide the Tosca server address. Look for the green checkmark for the correct address
领英推荐
-?????????Go to the “Set up logging” and check the “ToscaDistributionAgent.log” path. Note down the location.
-?????????Click on save and check for the green color agent to make sure it is running.
-?????????Navigate to Project -> Settings -> Commander -> DistributedExecution -> Server.
Specify the IP address and the port number on which you have configured Tosca server.
Ex: https://tri-nb1535.tricentis.com:81/DistributionServerService/ManagerService.svc?
-?????????Make sure you check in all and the workspace is closed.
Important tip - make sure you have the Tosca extension installed in the agent browser.
Tosca server
-?????????Go to “C:\Program Files (x86)\TRICENTIS\Tosca Server\DexServer” and open “Tricentis.DistributionServerService.exe.config”
-?????????Edit and provide the port number of the Tosca server for the base address for?CommunicationService.svc, ManagerService.svc, and MonitorService as below.
-?????????Save and close the notepad.
Tosca commander.
Create a workspace if the workspace is not already present using the same connection string which will connect the workspace to the common repository.
-?????????Login into workspace and go to Execution section -> Test Events -> New Test Event.
-?????????Drag and drop the configuration to?the newly created test event. Then drag and drop the?execution list onto the configuration. The hierarchy should look like this.
-?????????Navigate to Project -> Settings -> Commander -> DistributedExecution -> Server.
Specify the IP address and the port number on which you have configured the Tosca server.
Ex: https://tri-nb1535.tricentis.com:81/DistributionServerService/ManagerService.svc?
-?????????Perform check-in all operation.
?-?????????In Tosca commander go to the Configurations -> right-click and refresh. By doing this we will check if all the agents are available for the execution.
??-?????????Go to the Test event and trigger the execution.
?Abhishek - Dr. Tosca:?This is great. Can we use distributed execution with continuous integration?
Dr. Tosca – Abhishek: Yes Absolutely, Tosca commander supports the continuous integration and ToscaCI can be leveraged for this process. We can also integrate it with the external tool like Jenkins and ADO
?Abhishek - Dr. Tosca: Thank you, What else do I need to know about the distributed execution.
Dr. Tosca – Abhishek:?What we have just gone through was a basic setup of distributed execution for the demo purpose. We can modify/upgrade the setup as per our requirements.
I hope, you get all answers to your question. The solution prescribed will help you reduce the time of your testcase execution. I will come up again with interesting topics to help with your automation.
Till then, take care happy testing.
?
TOSCA Automation Tester | Certified AS1, AS2, TDS1, AE1 | Expertise in TOSCA TestSuite, TCD, TDS, and DEX
1 年Hi Parag.... could you please explain how unattended execution works in Tosca
Senior Quality Assurance Analyst at MAXIMUS
2 年Is it common for the DEX service to stop running due to excessive file size? I believe it is related to log files, but ours stops almost weekly and has to have log files cleared and the service restarted.
Pilot Architect | Partner Enablement | Avo Assure | Tosca Architect | NeoLoad Professional | Offbeat Traveller
2 年#network
VP Operational Excellence
2 年Awesome Parag Kukwas! Very helpful!
Head of Customer Experience Transformation | PMP | Global Enabler | CSM | Test Architect
2 年#network