Having recently set up a scheduling server and when running scheduled test lists, the DOM and the associated runtime images at the point of test failure are not available. The log entries indicate the file path for these files is invalid:
"[12/07 10:40:32,Telerik.TestStudio.ExecutionManagerService.exe(4312:53),TestStudio] AutomationHostState.LoadFailureImageFromDisk() : Invalid file path to load the bitmap from: C:\Windows\TEMP\ 130939764253142044_files\eReg ProjectInfoPage CUP NWFWMD_0_ImageOnFailure.png
[12/07 10:40:32,Telerik.TestStudio.ExecutionManagerService.exe(4312:53),TestStudio] AutomationHostState.LoadFailureDOMFromDisk() : Invalid file path to load the DOM from: C:\Windows\TEMP\ 130939764253142044_files\eReg ProjectInfoPage CUP NWFWMD_0_DomTreeOnFailure.txt"
How do I set up the correct file path? Any direction on how to resolve this error would be much appreciated!
Thanks,
Briar
10 Answers, 1 is accepted
This was a known bug in Test Studio which we fixed a little while ago. What build of Test Studio do you have installed? The latest build and release contains the fix for this problem
Regards,
Cody
Telerik
Rank 1
Hi, Cody.
I have version 2015.3.1015.0 installed on the client machine and the server machine.
Briar
Okay that explains it. The fix for this was included in our very next release which is an internal build, build number 2015.3.1112.
Regards,
Cody
Telerik
Rank 1
Thank you, Cody! I will install that version in the next day or two and see if it clears up the problem.
A second issue (which I can re-enter as a new issue if necessary) is I seem to have old versions of tests being used when the test lists are executed remotely. Is there a way to force an update of the test list code on the scheduling server?
Test Studio compares the date and time stamp of the test file on disk to the date and time stamp of the test stored in the scheduling server. It only uploads the test if the date and time stamp on disk is newer than what's stored in the storage server. This means the way you force a test to be uploaded to storage is by touching the date and time stamp of the test file itself. I'm referring to the .tstest file. This can also be done by making a benign change in the test itself and then saving everything to disk. This will force a new date and time stamp on the test.
Regards,
Cody
Telerik
Rank 1
Rank 1
While I've got you :) ...
Test lists scheduled remotely for immediate execution run successfully but test lists scheduled for recurring execution at specific times are failing. An excerpt of the application log at the beginning of the first scheduled test list:
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18)] First trace message from pool unnamed thread (managed ID = 18, native ID = 1152).
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobRunner.RunJobAsync() : Unable to load test list, aborting run.
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobRunner.RunJobAsync() : Use source control server: NO
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobRunner.RunJobAsync() : Project source location: I:\Application Development Team\TestStudio\briar-tests\Regression Tests
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobRunner.RunJobAsync() : Check if test list is available at project location. Consider cleaning Job storage!
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobRunner.RunJobAsync() : Job storage location: C:\Users\bparmer\AppData\Roaming\Telerik\TestStudio\Scheduler\ScheduleStorage
[12/07 18:00:59,Telerik.TestStudio.Scheduling.Client.exe(1156:18),Execution] JobBroker.ctor() : Job runner refused this job!
This type of message repeats over and over with different thread ids. How do I clean job storage? I see one file at the job storage location. Any other suggestions?
Thanks for your help!
Briar
Test Studio stores all scheduled jobs, including those that are set to recurring, in the job storage location. Each file you find there represents one scheduled job or one recurring job. Test Studio does this so that when the machine is rebooted or restarted it can pick up where it left off and maintain the scheduled test lists.
The standard way of deleting a schedule test list is to delete it from the results view as documented here. If that approach does not work what you can do is delete all of the files from the job storage folder. Then restart the Telerik scheduling service using the Windows services control panel. This will purge all scheduled test lists and make the scheduling service start again from scratch.
Regards,
Cody
Telerik
Rank 1
Cody, I really appreciate your help. It saved me a lot of time working through issues to get the scheduling server working for us. Thanks!
Briar
I'm glad I could help. Let me know if you need anything further.
Regards,
Cody
Telerik