Communication Error
Hi all, Distributed testing from my Win7 computer to another test-computer with Windows XP works. My computer is on our company domain and I have the tests executed by TestExecute on the comput...
Forum Discussion
Hi all,
I succeeded in trying the basics of distributed testing. SmartBear Support gave me some advice (many thanks for that!). For example I was advised to make sure that the latest version of the tools are installed and use TestComplete 9.20 and TestExecute 9.20 on both the master and slave machines. Another advice was checking whether the same ports for remote connections are used (http://support.smartbear.com/viewarticle/33058/), because the same port range must be used on all the computers involved in distributed testing. With my tests, this seemed to be the case because both machines are on default port 6090 because i changed nothing and was oblivious of this port-setting. These ports are not blocked by a firewall. I have also tried the advice of restarting the TestComplete 9 service on the slave machine (Control Panel | Administrative Tools | Services).
It took a lot of perseverance to get acquainted with setting NetworkSuite correctly and everything related, but in the end I go it to work with some trial tests. Note that I want to do a lot of things in sequence, so I have no multiple tasks within jobs to run simultaneously. It takes a lot more effort to have actual (complicated) tests in sequence run smoothly, wether it is locally or distributed, and this work is ongoing.
Maybe somebody can benefit from my trials and therefore; This is a summary of my eventually successful trials with the basics, so far:
(01) Install the latest TestComplete on the master machine with an administrator account.
(02) Install the same version TestExecute on the client machine administrator account.
(03) On the slave machine, ensure Remote Desktop sessions are allowed for the slave machine user (which in my case is the same user with the local administrator rights that installed TestExecute).
(04) On the slave machine, ensure there is a folder C:\Share which is shared to 'everyone' with full rights.
(05) You can log off on the slave machine or stay logged on, this seems to be of no importance.
(06) On the master machine, in TestComplete, create a New Project Suite.
(07) Add a TestComplete project to the Project Suite.
(08) Add some keyword and/or script tests to TestProject.
(09) Right click TestProject and Run to verify that the TestProject can run locally on the master machine in sequence according the list of test items of the TestProject.
(10) Add another project called DoDistributed to the Project Suite.
(11) Add a NetworkSuite to DoDistributed and set the deploy mode to 'automatic' (keep all other fields empty).
(12) Add a Host to this NetworkSuite with:
type in the ip address of the slave machine
keep login mode [Automatic (RDP Session)]
type in the domain of the slave machine user
type in the user name of the slave machine user
type in the password of the slave machine user
keep the source path [path to the current project suite]
type in the base path C:\Share
(13) Add a NetworkSuite to TestProject with the same settings as in (11) and (12).
(14) Add a Job called FirstJob to the NetworkSuite of DoDistributed.
(15) Add a Task to the Job, select the configured Host and set TestProject as Test (keep the rest default).
(16) Add another TestComplete called SecondTestProject project to the Project Suite.
(17) Add some keyword and/or script test(s) SecondTestProject.
(18) Disable in the TestSuite the project DoDistributed.
(19) Now, when the ProjectSuite is right-clicked and Run, TestProject should be performed locally first and SecondTestProject after that.
(20) Add a NetworkSuite to SecondTestProject with the same settings as in (11) and (12).
(21) Add another Job called SecondJob to the DoDistributed NetworkSuite.
(22) Add a Task to SecondJob, select the Host and set SecondTestProject as Test (keep the rest default).
(23) Jobs of the NetworkSuite of the DoDistributed project now contains FirstJob and SecondJob in sequence.
(24) Select NetworkSuite of DoDistributed (right-click and Run) to make sure the tests run on the slave machine.
(25) In the DoDistributed project, set as (one and only) ProjectTestItem, the NetworkSuite - NetworkSuite.
(26) Now DoDistributed can be set as default project and DoDistributed can be set as only enabled test project in the suite. (TestProject and SecondTestProject can be disabled in the root object of the Project Suite).
(27) When the ProjectSuite is run, on the slave machine TestProject runs distributed first and SecondTestProject after that.
I succeeded in trying the basics of distributed testing. SmartBear Support gave me some advice (many thanks for that!). For example I was advised to make sure that the latest version of the tools are installed and use TestComplete 9.20 and TestExecute 9.20 on both the master and slave machines. Another advice was checking whether the same ports for remote connections are used (http://support.smartbear.com/viewarticle/33058/), because the same port range must be used on all the computers involved in distributed testing. With my tests, this seemed to be the case because both machines are on default port 6090 because i changed nothing and was oblivious of this port-setting. These ports are not blocked by a firewall. I have also tried the advice of restarting the TestComplete 9 service on the slave machine (Control Panel | Administrative Tools | Services).
It took a lot of perseverance to get acquainted with setting NetworkSuite correctly and everything related, but in the end I go it to work with some trial tests. Note that I want to do a lot of things in sequence, so I have no multiple tasks within jobs to run simultaneously. It takes a lot more effort to have actual (complicated) tests in sequence run smoothly, wether it is locally or distributed, and this work is ongoing.
Maybe somebody can benefit from my trials and therefore; This is a summary of my eventually successful trials with the basics, so far:
(01) Install the latest TestComplete on the master machine with an administrator account.
(02) Install the same version TestExecute on the client machine administrator account.
(03) On the slave machine, ensure Remote Desktop sessions are allowed for the slave machine user (which in my case is the same user with the local administrator rights that installed TestExecute).
(04) On the slave machine, ensure there is a folder C:\Share which is shared to 'everyone' with full rights.
(05) You can log off on the slave machine or stay logged on, this seems to be of no importance.
(06) On the master machine, in TestComplete, create a New Project Suite.
(07) Add a TestComplete project to the Project Suite.
(08) Add some keyword and/or script tests to TestProject.
(09) Right click TestProject and Run to verify that the TestProject can run locally on the master machine in sequence according the list of test items of the TestProject.
(10) Add another project called DoDistributed to the Project Suite.
(11) Add a NetworkSuite to DoDistributed and set the deploy mode to 'automatic' (keep all other fields empty).
(12) Add a Host to this NetworkSuite with:
type in the ip address of the slave machine
keep login mode [Automatic (RDP Session)]
type in the domain of the slave machine user
type in the user name of the slave machine user
type in the password of the slave machine user
keep the source path [path to the current project suite]
type in the base path C:\Share
(13) Add a NetworkSuite to TestProject with the same settings as in (11) and (12).
(14) Add a Job called FirstJob to the NetworkSuite of DoDistributed.
(15) Add a Task to the Job, select the configured Host and set TestProject as Test (keep the rest default).
(16) Add another TestComplete called SecondTestProject project to the Project Suite.
(17) Add some keyword and/or script test(s) SecondTestProject.
(18) Disable in the TestSuite the project DoDistributed.
(19) Now, when the ProjectSuite is right-clicked and Run, TestProject should be performed locally first and SecondTestProject after that.
(20) Add a NetworkSuite to SecondTestProject with the same settings as in (11) and (12).
(21) Add another Job called SecondJob to the DoDistributed NetworkSuite.
(22) Add a Task to SecondJob, select the Host and set SecondTestProject as Test (keep the rest default).
(23) Jobs of the NetworkSuite of the DoDistributed project now contains FirstJob and SecondJob in sequence.
(24) Select NetworkSuite of DoDistributed (right-click and Run) to make sure the tests run on the slave machine.
(25) In the DoDistributed project, set as (one and only) ProjectTestItem, the NetworkSuite - NetworkSuite.
(26) Now DoDistributed can be set as default project and DoDistributed can be set as only enabled test project in the suite. (TestProject and SecondTestProject can be disabled in the root object of the Project Suite).
(27) When the ProjectSuite is run, on the slave machine TestProject runs distributed first and SecondTestProject after that.