Distributed testing: Cannot load the remote project. Reason: Timeout Expired
Hi, Wehave a master machine with a Master suitethat start our Slave suite(UI tests) on different VMs. The master machine and the VMs have all the same version of TestComplete and TestExecute (12.10.590.7). Recently an exception is causing us a lot of issues. When we run the tests from the master on our VMs, sometimes it is not working because of the exception: "Cannot load the remote project. Failed to invoke an object. Reason: timeout expired" and "Cannot close the remote instance of TestComplete(TestExecute). Object disconnected". (Please see the screenshot) This exception seems to occur when the task associated to the VM is the State 2: Initializing. This exception is not happening all the time and not alwaysthe same VMs. It is causing a lot of problem for us because we need to repeat the tests that didn't run again and again. What is the timeout which is mentioned in the exception ? Does anybody has faced the same issue ? Thank you for your help, CamilleDistributed Testing: Host Object disconnected
Hi all, we are running into a recurrent issue with our UI Distributed Testing. We are using TestComplete 12.10 on all our machines. Master project is running on QA Master VM. This Master project run different Slave project on several QA Slave VMs. Each VM has a Host associated with it. Time to time we are experiencing an issue with some Hosts: Object Disconnected. In our process we are verifyng the Host manually before starting tests on it: if(task.Host.Verify(10))//TimeOut of 5min { //Run the tests } If the Host can be verified, we run the particular taskon this Host. Running means TestComplete will first Fast Verify the host of the task(State: ( 9 -ns_FastVerifying), then Initialize (State: 2 -ns_Initializing) and finally Run the tests (State: 3 -ns_Running). Please check this page for further information. But sometimes the timeout associated with the host expires when TestComplete perform the Fast Verification, even though we performed the verification manually in the code just before. So the verification failed, so does the task... (default timeout on each hostis 10min) TestComplete then log an error : Object Disconnected TestComplete does not give any more information about the issue... Is there a way to have better understanding on the issue ? (I tried to look into Event Viewer on the specified Host but didn't find anything related) Is this something related to TestCompleteService that crashed ? Maybe this is an issue with our VMs, so we want to know if anyone has ever experienced this issue ?? Thanks for your feedback and answers, Camille
Distributed Testing - Test Execute never moves on to 2nd test if 1st test is too long???
Background - My Project suite has multiple projects, each is ONLY ran in a distributed setup. The Project is ran every night on a Master VM using TestExecute. The Network Project contains 4 tests: 1: Job One / Task One - deploys to a VM to test in Chrome Project One) 2: Job Two / Task Two - deploys to a VM to test in Chrome (Project Two) 3: Job Three / Job Three - The job contains two tasks, deploys to separate VM's to test customer-facing site in different browsers (Project Three 4: Script / Send Email - script under Network Project that saves the test log and emails it to various business owners (Network Project / Advanced / Script) The problem: The first test under the Network Project can be quite long, sometimes taking up to three hours. After it finishes (I receive an email when it finishes via a script) it never moves on to the 2nd job, but just hangs indefinitely. However, if I disable all but a few of the tests within the Project One, thus greatly reducing the time Network Project Test One takes to run, it moves on to Network Project Test Two with no problem. I don't understand why that would happen. I have one test within Project One that fails every night, but it moves on to the other with no problems; also, if I manually force one of the tests to fail during short run as described above, the Network Project still moves on to the next test/job. No to mention that I also have failures in Test 2, and Test 3 doesn't fail to start. If there was a setting somewhere that I needed to change (a "if test takes longer than 2 hours" setting, something like that), I would have expected TE to close after a time instead of just hanging. I come back into the office in the morning and TE still says "Running" in the corner, but it's not doing anything. I couldprobablyturnall of the tests into tasks under 1 job, thus they will all run in parallel. But then TE will just hang and never execute the Send Email test, and since I want it to run after everything has finished that won’t really work. Also, each task is set up Action After Run=Log off from computer and UsePrevious Instance=Restart TestComplete. Don't know if that is relevant or not, but it feels like it. Any help would be greatly appreciated. Thanks!!!
