8 Answers, 1 is accepted
This is an error we are familiar with but have not been able to reproduce. The error is generic and we cannot troubleshoot the issue based on it alone.
Can you send us your complete test project with repro steps so we can test it locally? If you consider the information too sensitive for a public forum, please open a support ticket. Unlike a forum thread, a support ticket is confidential. Please include a reference to this thread in the ticket.
All the best,
Anthony
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
I found out I'd not got the latest internal build my version (2010.3) so I installed the latest, and all is fixed.
Cheers
Clive
Hey Anthony,
My scripts are running fine when I run individually but not in Test List. In one machine, More than 2 scripts are not running in the Test List in the other machine, Test List is not at all running. I'm seeing below error:
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:6),Framework] BrowserProvisioner.ServiceThread() : A new client has connected to the provisioning pipe but this will be treated as a termination cue.
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:4),Framework] BrowserProvisioner.EndService() : Provisioning thread terminated.
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:4),DialogPlayback] DialogMonitor.AddDialog() : Added {OnBeforeUnloadDialog(Dismiss=OK)} for monitoring.
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:4),Framework] Manager.RemoveBrowser() : Removed client ID "e2893631-a201-4249-8cbd-2e016f363474" (0 remaining).
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:4),Framework] Manager.SetActiveBrowser() : Active browser is now null.
[10/16 15:18:40,ArtOfTest.Runner.exe(8228:4),Warning] Manager.RemoveBrowser() : Attempted to remove a client ID "e2893631-a201-4249-8cbd-2e016f363474" that was not in the list.
[10/16 15:18:41,ArtOfTest.Runner.exe(8228:4),DialogPlayback] DialogMonitor.Stop() : Dialog monitoring is being halted.
[10/16 15:18:41,ArtOfTest.Runner.exe(8228:4),UIAutomation] AutomationExtensions.AddAutomationEventHandler() : Added a(n) WindowPatternIdentifiers.WindowOpenedProperty handler on element System.Windows.Automation.AutomationElement scope Descendants.
[10/16 15:18:41,Telerik.TestStudio.Desktop.exe(8064:12)] First trace message from background thread "Callback Listener Thread" (managed ID = 12, native ID = 9068).
[10/16 15:18:41,Telerik.TestStudio.Desktop.exe(8064:12),Warning] PipeCommunication.SyncPipeRead() : Pipe was already disposed at the moment of the read attempt.
Please review and advise.
Thanks for reaching us out.
Please note that you are referring to a post over six years old and probably the issue you are facing has nothing to do with the information listed above.
Therefore I would like to kindly ask you to elaborate more on the current Test Studio version you have, the setup you have configured - if using multiple execution machines or a single one, are the test lists scheduled, ran locally or remotely, etc.
Depending on the above information I would like to have the log files wither of the local machine or the remote one. Please note to clear the logs prior reproducing the reported inconsistency to ensure only relative to the current issue records will be stored within the files. Once collected you could zip these and send them via this thread for further investigation.
Thank you in advance for your understanding and cooperation!
Regards,
Elena Tsvetkova
Progress Telerik
Hey Elena,
Thank you so much for the quick response!
Well, as you asked I've put all the information together and attached the zip file, please find it and advise.
Best,
-Pavan
Hey Elena,
I found that the Scenario 1 log file is empty. Sorry about that and here I'm attaching the same again for your reference.
Best,
Pavan
Thanks for getting back.
Please allow me some time to review the provided details and I will get back to you as soon as possible. Thanks!
Regards,
Elena Tsvetkova
Progress Telerik
Thank you for allowing me some time.
I reviewed the provided details and here is what I have noticed.
In regards to the remote execution the listed exception is the following:
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
This could happen if the project root folder has too long path - when executing a test list remotely the project is deployed to the execution machine to a temp folder which is concatenated to the test list full path and this string should be less than 260 characters, This is a Windows limitation for the full path name of a file. Please reduce the length of the project root folder as well as the names of the tests and folders in its structure.
The local execution log file seems to not be full though I would advise you double check the test list's settings especially what browsers are listed there as execution browsers. The test list settings override the test's ones and this might be the reason for the tests to run against different browsers. Please in case the local execution is still not consistent generate the log file again and if the run hangs please leave it for a while so that any exception could be listed in the log.
Thank you in advance!
Regards,
Elena Tsvetkova
Progress Telerik